05059724f8
Summaries as implemented cannot be aggregated in a meaningful way. Partitoning them by status code and method only made sense if we were interested in the individual latency and size of e.g. GET request that result in status 503. In general, that's not the case. Most of the time, the user will be interested in the latency and size of _all_ HTTP requests. (With future changes to client_golang, we will consider making the HTTP instrumentation configurable, e.g. to handle the case where the user is only interested in the latency of successful requests.) |
||
|---|---|---|
| _vendor | ||
| examples | ||
| extraction | ||
| model | ||
| prometheus | ||
| text | ||
| .gitignore | ||
| .travis.yml | ||
| LICENSE | ||
| Makefile | ||
| README.md | ||
README.md
Overview
This is the Prometheus Go client library. It provides several distinct functions, and there is separate documentation for each respective component. You will want to select the appropriate topic below to continue your journey:
-
See the exposition library if you want to export metrics to a Prometheus server or pushgateway
-
See the consumption library if you want to process metrics exported by a Prometheus client. (The Prometheus server is using that library.)
Getting Started
- The source code is periodically indexed: Go Exposition Client.
- All of the core developers are accessible via the Prometheus Developers Mailinglist.
Testing
$ go test ./...
Continuous Integration
Contributing
See the contributing guidelines for the Prometheus server.