2020-05-24 23:13:21 +05:30
---
stage: Monitor
group: APM
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
---
2019-02-15 15:39:39 +05:30
# Prometheus Metrics library
2020-03-09 13:42:32 +05:30
> [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/merge_requests/8935) in GitLab 9.0.
2019-02-15 15:39:39 +05:30
GitLab offers automatic detection of select [Prometheus exporters ](https://prometheus.io/docs/instrumenting/exporters/ ).
## Exporters
Currently supported exporters are:
- [Kubernetes ](kubernetes.md )
- [NGINX ](nginx.md )
- [NGINX Ingress Controller 0.9.0-0.15.x ](nginx_ingress_vts.md )
- [NGINX Ingress Controller 0.16.0+ ](nginx_ingress.md )
- [HAProxy ](haproxy.md )
- [Amazon Cloud Watch ](cloudwatch.md )
We have tried to surface the most important metrics for each exporter, and will
be continuing to add support for additional exporters in future releases. If you
would like to add support for other official exporters, contributions are welcome.
## Identifying Environments
GitLab retrieves performance data from the configured Prometheus server, and
attempts to identifying the presence of known metrics. Once identified, GitLab
then needs to be able to map the data to a particular environment.
In order to isolate and only display relevant metrics for a given environment,
GitLab needs a method to detect which labels are associated. To do that,
GitLab uses the defined queries and fills in the environment specific variables.
Typically this involves looking for the
2019-03-02 22:35:43 +05:30
[`$CI_ENVIRONMENT_SLUG` ](../../../../ci/variables/README.md#predefined-environment-variables ),
2019-02-15 15:39:39 +05:30
but may also include other information such as the project's Kubernetes namespace.
Each search query is defined in the [exporter specific documentation ](#exporters ).
