mirror
/
client_golang
mirror of https://github.com/prometheus/client_golang.git
1
0
Fork 1
Code Issues Packages Projects Releases Wiki Activity
Prometheus instrumentation library for Go applications
1,429 Commits 30 Branches 52 Tags 24 MiB
Go 99.2%
Makefile 0.3%
C 0.3%
Dockerfile 0.1%
Go to file
Quentin D fae2f6306b
Add constrained labels and Constrained variant for all MetricVecs (#1151) 
* Introduce MetricVecOpts and add constraints to VariableLabels

MetricVecOpts exposes options specific to MetricVec initialisation. The
first option exposed by MetricVecOpts are constraints on VariableLabels,
allowing restrictions on the possible values a label can take, to
prevent cardinality explosion when the label value comes from a
non-trusted source (as a user input or HTTP header).

Signed-off-by: Quentin Devos <4972091+Okhoshi@users.noreply.github.com>

* Add tests

Signed-off-by: Quentin Devos <4972091+Okhoshi@users.noreply.github.com>

Signed-off-by: Quentin Devos <4972091+Okhoshi@users.noreply.github.com>
 		2022-12-13 13:47:52 +01:00
.circleci Test and support 1.19 (#1160) 2022-11-08 00:14:19 +01:00
.github Update common Prometheus files (#1111) 2022-08-05 22:38:30 +02:00
api Test and support 1.19 (#1160) 2022-11-08 00:14:19 +01:00
examples examples: Add exemplars and middleware examples (#1173) 2022-11-22 22:42:31 +01:00
prometheus Add constrained labels and Constrained variant for all MetricVecs (#1151) 2022-12-13 13:47:52 +01:00
scripts Enable same linters as the Prometheus repo itself (#1056) 2022-06-17 09:04:06 +02:00
.gitignore prometheus: Fix convention violating names for generated collector metrics (#1048) 2022-05-09 10:33:45 +02:00
.go-version Generate new Go runtime metrics for go 1.19 (#1105) 2022-08-05 15:48:33 +02:00
.golangci.yml fix assorted oddities found by golangci-lint (#1040) 2022-08-03 06:30:51 +02:00
CHANGELOG.md Cut v1.14.0 2022-11-08 05:00:31 +01:00
CODE_OF_CONDUCT.md Update common Prometheus files (#1045) 2022-05-05 07:46:54 +02:00
CONTRIBUTING.md Mention the DCO in the contributing guide 2018-05-31 14:22:30 +00:00
Dockerfile prometheus: Fix convention violating names for generated collector metrics (#1048) 2022-05-09 10:33:45 +02:00
LICENSE License cleanup 2015-01-22 16:13:15 +01:00
MAINTAINERS.md Change maintainers from @beorn7 to @bwplotka/@kakkoyun (#873) 2021-06-01 14:13:09 +01:00
Makefile Generate new Go runtime metrics for go 1.19 (#1105) 2022-08-05 15:48:33 +02:00
Makefile.common Update common Prometheus files (#1064) 2022-06-14 00:19:38 +02:00
NOTICE Create a public registry interface and separate out HTTP exposition 2016-08-02 18:46:22 +02:00
README.md Added tip from Björn + Grammarly. 2022-11-01 16:54:19 +00:00
SECURITY.md Update common Prometheus files (#1045) 2022-05-05 07:46:54 +02:00
VERSION Cut v1.14.0 2022-11-08 05:00:31 +01:00
go.mod Update prometheus/client_model dependency 2022-10-19 18:27:50 +02:00
go.sum Update prometheus/client_model dependency 2022-10-19 18:27:50 +02:00

README.md

Prometheus Go client library

CircleCI Go Report Card Go Reference Slack

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.17 or later.

Important note about releases and stability

This repository generally follows Semantic Versioning. However, the API client in prometheus/client_golang/api/… is still considered experimental. Breaking changes of the API client will not trigger a new major release. The same is true for selected other new features explicitly marked as EXPERIMENTAL in CHANGELOG.md.

Features that require breaking changes in the stable parts of the repository are being batched up and tracked in the v2 milestone. The v2 development happens in a separate branch for the time being. v2 releases off that branch will happen once sufficient stability is reached. In view of the widespread use of this repository, v1 and v2 will coexist for a while to enable a convenient transition.

Instrumenting applications

code-coverage Go Reference

The prometheus directory contains the instrumentation library. See the guide on the Prometheus website to learn more about instrumenting applications.

The examples directory contains simple examples of instrumented code.

Client for the Prometheus HTTP API

code-coverage Go Reference

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.

clint_golang community is also present on the CNCF Slack #prometheus-client_golang.

For Maintainers: Release Process

To cut a minor version:

  1. Create a new branch release-<major>.<minor> on top of the main commit you want to cut the version from and push it.
  2. Create a new branch on top of the release branch, e.g. <yourname>/cut-<major>.<minor>.<patch>,
  3. Change the VERSION file.
  4. Update CHANGELOG (only user-impacting changes to mention).
  5. Create PR, and get it reviewed.
  6. Once merged, create a release with the release-<major>.<minor> tag on GitHub with the <version> / <date> title.
  7. Announce on the prometheus-announce mailing list, slack and Twitter.
  8. Merge the release branch back to the main using the "merge without squashing" approach (!).

NOTE: In case of merge conflicts, you can checkout the release branch in a new branch, e.g. /resolve-conflicts, fix the merge problems there, and then do a PR into main from the new branch. In that way, you still get all the commits in the release branch back into main`, but leave the release branch alone.

To cut the patch version:

  1. Create a branch on top of the release branch you want to use.
  2. Cherry-pick the fixes from the main branch (or add new commits) to fix critical bugs for that patch release.
  3. Follow steps 3-8 as above.