14730c70c0
As it turned out, it's not that esay to guess "common" combination of interface upgrades. So I decided to just implement all 32 possible combination of interface upgrades. (Only 16 with Go 1.7 and earlier.) Clearly, this calls for code generation. But right now, we still need to find out what's the best form of the code. For later additions, implementing code generation might be useful. Note that newDelegator is called for each HTTP request. Thus, this commit aims to make the upgrade selection quick. (After the type checks, it's just directly accessing an element in a slice.) |
||
|---|---|---|
| api | ||
| examples | ||
| prometheus | ||
| .gitignore | ||
| .travis.yml | ||
| CHANGELOG.md | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| 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. It is still in alpha stage.
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.