89ca0458cb
This finally makes the (presumably) common simple case as simple as it gets. The still quite common (but less common) case of using a Gauge is slightly more verbose now, but not needing to provide a separate constructor is totally worth it. Finally, the advanced use case is not really more verbose as in my original suggestion. However, the logic to decide which Observer to use is now all in the ObserverFunc handed in at construction time. This is deliberate and desired. It makes sure the selection mechanism is all spelled out there. No surprises buried deep in the function code somewhere. |
||
|---|---|---|
| api/prometheus | ||
| examples | ||
| prometheus | ||
| .gitignore | ||
| .travis.yml | ||
| AUTHORS.md | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| NOTICE | ||
| README.md | ||
| VERSION | ||
README.md
Prometheus Go client library
This is the Go client library for Prometheus. It has two separate parts, one for instrumenting application code, and one for creating clients that talk to the Prometheus HTTP API.
Instrumenting applications
The
prometheus directory
contains the instrumentation library. See the
best practices section of the
Prometheus documentation to learn more about instrumenting applications.
The
examples directory
contains simple examples of instrumented code.
Client for the Prometheus HTTP API
The
api/prometheus directory
contains the client for the
Prometheus HTTP API. It allows you
to write Go applications that query time series data from a Prometheus server.
Where is model, extraction, and text?
The model packages has been moved to
prometheus/common/model.
The extraction and text packages are now contained in
prometheus/common/expfmt.
Contributing and community
See the contributing guidelines and the Community section of the homepage.