2017-02-08 05:38:24 -05:00
|
|
|
# GitLab Prometheus
|
|
|
|
|
|
|
|
>**Notes:**
|
2017-02-08 07:40:11 -05:00
|
|
|
- Prometheus and the various exporters listed in this page are bundled in the
|
|
|
|
Omnibus GitLab package. Check each exporter's documentation for the timeline
|
|
|
|
they got added. For installations from source you will have to install
|
2017-02-08 05:38:24 -05:00
|
|
|
them yourself. Over subsequent releases additional GitLab metrics will be
|
|
|
|
captured.
|
|
|
|
- Prometheus services are off by default but will be on starting with GitLab 9.0.
|
2017-02-09 03:44:05 -05:00
|
|
|
- Prometheus and its exporters do not authenticate users, and will be available
|
|
|
|
to anyone who can access them.
|
2017-02-08 05:38:24 -05:00
|
|
|
|
|
|
|
[Prometheus] is a powerful time-series monitoring service, providing a flexible
|
|
|
|
platform for monitoring GitLab and other software products.
|
|
|
|
GitLab provides out of the box monitoring with Prometheus, providing easy
|
|
|
|
access to high quality time-series monitoring of GitLab services.
|
|
|
|
|
|
|
|
## Overview
|
|
|
|
|
|
|
|
Prometheus works by periodically connecting to data sources and collecting their
|
2017-02-08 07:40:11 -05:00
|
|
|
performance metrics via the [various exporters](#prometheus-exporters). To view
|
|
|
|
and work with the monitoring data, you can either
|
|
|
|
[connect directly to Prometheus](#viewing-performance-metrics) or utilize a
|
|
|
|
dashboard tool like [Grafana].
|
2017-02-08 05:38:24 -05:00
|
|
|
|
|
|
|
## Configuring Prometheus
|
|
|
|
|
|
|
|
>**Note:**
|
|
|
|
Available since Omnibus GitLab 8.16. For installations from source you'll
|
|
|
|
have to install and configure it yourself.
|
|
|
|
|
|
|
|
To enable Prometheus:
|
|
|
|
|
|
|
|
1. Edit `/etc/gitlab/gitlab.rb`
|
|
|
|
1. Find and uncomment the following line, making sure it's set to `true`:
|
|
|
|
|
|
|
|
```ruby
|
|
|
|
prometheus['enable'] = true
|
|
|
|
```
|
|
|
|
|
|
|
|
1. Save the file and [reconfigure GitLab][reconfigure] for the changes to
|
|
|
|
take effect
|
|
|
|
|
|
|
|
By default, Prometheus will run as the `gitlab-prometheus` user and listen on
|
2017-02-09 03:44:05 -05:00
|
|
|
`http://localhost:9090`. If the [node exporter](#node-exporter) service
|
2017-02-08 05:38:24 -05:00
|
|
|
has been enabled, it will automatically be set up as a monitoring target for
|
|
|
|
Prometheus.
|
|
|
|
|
2017-02-08 07:40:11 -05:00
|
|
|
## Viewing performance metrics
|
2017-02-08 05:38:24 -05:00
|
|
|
|
|
|
|
After you have [enabled Prometheus](#configuring-prometheus), you can visit
|
2017-02-09 03:44:05 -05:00
|
|
|
`http://localhost:9090` for the dashboard that Prometheus offers by default.
|
|
|
|
|
|
|
|
>**Note:**
|
|
|
|
If SSL has been enabled on your GitLab instance, you may not be able to access
|
|
|
|
Prometheus on the same browser as GitLab due to [HSTS][hsts]. We plan to
|
|
|
|
[provide access via GitLab][multi-user-prometheus], but in the interim there are
|
|
|
|
some workarounds: using a separate browser for Prometheus, resetting HSTS, or
|
2017-02-09 03:48:03 -05:00
|
|
|
having [Nginx proxy it][nginx-custom-config]. Follow issue [#27069] for more
|
|
|
|
information.
|
2017-02-08 05:38:24 -05:00
|
|
|
|
|
|
|
The performance data collected by Prometheus can be viewed directly in the
|
|
|
|
Prometheus console or through a compatible dashboard tool.
|
|
|
|
The Prometheus interface provides a [flexible query language][prom-query] to work
|
|
|
|
with the collected data where you can visualize their output.
|
|
|
|
For a more fully featured dashboard, Grafana can be used and has
|
|
|
|
[official support for Prometheus][prom-grafana].
|
|
|
|
|
2017-02-09 03:44:05 -05:00
|
|
|
Sample Prometheus queries:
|
|
|
|
|
|
|
|
- **% Memory used:** `(1 - ((node_memory_MemFree + node_memory_Cached) / node_memory_MemTotal)) * 100`
|
|
|
|
- **% CPU load:** `1 - rate(node_cpu{mode="idle"}[5m])`
|
|
|
|
- **Data transmitted:** `irate(node_network_transmit_bytes[5m])`
|
|
|
|
- **Data received:** `irate(node_network_receive_bytes[5m])`
|
|
|
|
|
2017-02-08 05:38:24 -05:00
|
|
|
## Prometheus exporters
|
|
|
|
|
|
|
|
There are a number of libraries and servers which help in exporting existing
|
|
|
|
metrics from third-party systems as Prometheus metrics. This is useful for cases
|
|
|
|
where it is not feasible to instrument a given system with Prometheus metrics
|
|
|
|
directly (for example, HAProxy or Linux system stats). You can read more in the
|
2017-02-08 07:40:11 -05:00
|
|
|
[Prometheus exporters and integrations upstream documentation][prom-exporters].
|
2017-02-08 05:38:24 -05:00
|
|
|
|
|
|
|
While you can use any exporter you like with your GitLab installation, the
|
|
|
|
following ones documented here are bundled in the Omnibus GitLab packages
|
|
|
|
making it easy to configure and use.
|
|
|
|
|
|
|
|
### Node exporter
|
|
|
|
|
2017-02-08 07:40:11 -05:00
|
|
|
The node exporter allows you to measure various machine resources such as
|
2017-02-08 05:38:24 -05:00
|
|
|
memory, disk and CPU utilization.
|
|
|
|
|
2017-02-08 07:40:11 -05:00
|
|
|
[➔ Read more about the node exporter.](node_exporter.md)
|
2017-02-08 05:38:24 -05:00
|
|
|
|
2017-02-08 08:29:02 -05:00
|
|
|
### Redis exporter
|
|
|
|
|
|
|
|
The Redis exporter allows you to measure various Redis metrics.
|
|
|
|
|
|
|
|
[➔ Read more about the Redis exporter.](redis_exporter.md)
|
|
|
|
|
2017-02-08 08:40:28 -05:00
|
|
|
### Postgres exporter
|
|
|
|
|
|
|
|
The Postgres exporter allows you to measure various PostgreSQL metrics.
|
|
|
|
|
|
|
|
[➔ Read more about the Postgres exporter.](postgres_exporter.md)
|
|
|
|
|
2017-02-08 09:44:56 -05:00
|
|
|
### GitLab monitor exporter
|
|
|
|
|
|
|
|
The GitLab monitor exporter allows you to measure various GitLab metrics.
|
|
|
|
|
|
|
|
[➔ Read more about the GitLab monitor exporter.](gitlab_monitor_exporter.md)
|
|
|
|
|
2017-02-08 05:38:24 -05:00
|
|
|
[grafana]: https://grafana.net
|
2017-02-09 03:44:05 -05:00
|
|
|
[hsts]: https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security
|
|
|
|
[multi-user-prometheus]: https://gitlab.com/gitlab-org/multi-user-prometheus
|
|
|
|
[nginx-custom-config]: https://docs.gitlab.com/omnibus/settings/configuration.html#inserting-custom-nginx-settings-into-the-gitlab-server-block
|
2017-02-08 05:38:24 -05:00
|
|
|
[prometheus]: https://prometheus.io
|
2017-02-09 03:44:05 -05:00
|
|
|
[prom-exporters]: https://prometheus.io/docs/instrumenting/exporters/
|
2017-02-08 05:38:24 -05:00
|
|
|
[prom-query]: https://prometheus.io/docs/querying/basics
|
|
|
|
[prom-grafana]: https://prometheus.io/docs/visualization/grafana/
|
|
|
|
[scrape-config]: https://prometheus.io/docs/operating/configuration/#%3Cscrape_config%3E
|
|
|
|
[reconfigure]: ../../restart_gitlab.md#omnibus-gitlab-reconfigure
|
2017-02-09 03:48:03 -05:00
|
|
|
[#27069]: https://gitlab.com/gitlab-org/gitlab-ce/issues/27069
|