You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This results in an ArangoDB Exporter exposing all statistics of
18
+
the ArangoDB server (running at `http://<your-database-host>:8529`)
19
+
at `http://<your-host-ip>:9101/metrics`.
20
+
21
+
## Exporter mode
22
+
23
+
Expose ArangoDB metrics for ArangoDB >= 3.6.0
24
+
25
+
In default mode metrics provided by ArangoDB `_admin/metrics` (<=3.7) or `_admin/metrics/v2` (3.8+) are exposed on Exporter port.
26
+
27
+
## Configuring Prometheus
28
+
29
+
There are several ways to configure Prometheus to fetch metrics from the ArangoDB Exporter.
30
+
31
+
Below you're find a sample Prometheus configuration file that can be used to fetch
32
+
metrics from an ArangoDB exporter listening on localhost port 9101 (without TLS).
33
+
34
+
```yaml
35
+
global:
36
+
scrape_interval: 15s
37
+
scrape_configs:
38
+
- job_name: arangodb
39
+
static_configs:
40
+
- targets: ['localhost:9101']
41
+
```
42
+
43
+
For more info on configuring Prometheus go to [its configuration documentation](https://prometheus.io/docs/prometheus/latest/configuration/configuration).
44
+
45
+
If you're using the [Prometheus Operator](https://github.com/coreos/prometheus-operator)
46
+
in Kubernetes, you need to create an additional `Service` and a `ServiceMonitor` resource
47
+
like this:
48
+
49
+
```yaml
50
+
kind: Service
51
+
apiVersion: v1
52
+
metadata:
53
+
name: arangodb-exporters-service
54
+
labels:
55
+
app: arangodb-exporter
56
+
spec:
57
+
selector:
58
+
app: arangodb-exporter
59
+
ports:
60
+
- name: metrics
61
+
port: 9101
62
+
63
+
---
64
+
65
+
apiVersion: monitoring.coreos.com/v1
66
+
kind: ServiceMonitor
67
+
metadata:
68
+
name: arangodb-exporter
69
+
namespace: monitoring
70
+
labels:
71
+
team: frontend
72
+
prometheus: kube-prometheus
73
+
spec:
74
+
namespaceSelector:
75
+
matchNames:
76
+
- default
77
+
selector:
78
+
matchLabels:
79
+
app: arangodb-exporter
80
+
endpoints:
81
+
- port: metrics
82
+
scheme: https
83
+
tlsConfig:
84
+
insecureSkipVerify: true
85
+
```
86
+
87
+
Note 1: that the typical deployment on the Prometheus operator is done in
88
+
a namespace called `monitoring`. Make sure to match the `namespace`
89
+
of the `ServiceMonitor` to match that.
90
+
91
+
Note 2: that the `Prometheus` custom resource has a field called `serviceMonitorSelector`.
92
+
Make sure that the `matchLabels` selector in there matches the labels of
0 commit comments