ec06aca188
When those are published on Dockerhub, people will be able to start those examples in fewer steps than the current documentation: https://prometheus.io/docs/introduction/getting_started/#starting-up-some-sample-targets While relying on Docker may not be always wished, giving the possibility to quickly start a daemon that exposes metrics can be useful in many tutorials. The simple and random example are build as static binaries and packaged as single binaries in Docker images. This commit tries really hard to limit the number of per-example maintenance work by sharing most of the Makefile to build the Docker images. The tiny top level Makefiles in each example directory are strictly identical. Updates: #347 |
||
|---|---|---|
| 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.
This library requires Go1.7 or later.
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.