aboutsummaryrefslogtreecommitdiffstats
path: root/vendor/github.com/prometheus/procfs/CONTRIBUTING.md
diff options
context:
space:
mode:
authorPalash Oswal <oswalpalash@gmail.com>2021-05-26 15:49:00 +0530
committerGitHub <noreply@github.com>2021-05-26 12:19:00 +0200
commit1f4e6ed95868861aae449b3630e6cfe5a2b96c93 (patch)
treeded977da86c36bdb3d07a03fa6341ed067645eef /vendor/github.com/prometheus/procfs/CONTRIBUTING.md
parent750ce1649cc6e2b51bc65b574f6a71399980af4c (diff)
syz-manager: add prometheus metrics
* syz-manager: add prometheus metrics Add prometheus metrics client to syz-manager. Expose metrics on a new port defined in mgrconfig. Allows for prometheus to scrape metrics from syz-manager. * syz-manager: expose metrics endpoint in http server .gitignore : remove local .img path * mgrconfig: remove unnecessary config option * syz-manager: update stats to use gaugefunc added docs for prometheus exported metrics added more gaugefunc metrics Signed-off-by: Palash Oswal <oswalpalash@gmail.com> * syz-manager: minor changes for CI tests added periods to comments and renamed go variables Signed-off-by: Palash Oswal <oswalpalash@gmail.com> * syz-manager: re-position prometheus counter declaration docs updated with PR comments Signed-off-by: Palash Oswal <oswalpalash@gmail.com>
Diffstat (limited to 'vendor/github.com/prometheus/procfs/CONTRIBUTING.md')
-rw-r--r--vendor/github.com/prometheus/procfs/CONTRIBUTING.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/vendor/github.com/prometheus/procfs/CONTRIBUTING.md b/vendor/github.com/prometheus/procfs/CONTRIBUTING.md
new file mode 100644
index 000000000..40503edbf
--- /dev/null
+++ b/vendor/github.com/prometheus/procfs/CONTRIBUTING.md
@@ -0,0 +1,18 @@
+# Contributing
+
+Prometheus uses GitHub to manage reviews of pull requests.
+
+* If you have a trivial fix or improvement, go ahead and create a pull request,
+ addressing (with `@...`) the maintainer of this repository (see
+ [MAINTAINERS.md](MAINTAINERS.md)) in the description of the pull request.
+
+* If you plan to do something more involved, first discuss your ideas
+ on our [mailing list](https://groups.google.com/forum/?fromgroups#!forum/prometheus-developers).
+ This will avoid unnecessary work and surely give you and us a good deal
+ of inspiration.
+
+* Relevant coding style guidelines are the [Go Code Review
+ Comments](https://code.google.com/p/go-wiki/wiki/CodeReviewComments)
+ and the _Formatting and style_ section of Peter Bourgon's [Go: Best
+ Practices for Production
+ Environments](http://peter.bourgon.org/go-in-production/#formatting-and-style).