451882b7e9
So far it was only possible to monitor single instance Gerrit servers.
This was due to to the fact that a URL had to be used that pointed to
a dedicated instance, since if multiple replicas would be behind the
instance, the metrics of a random replica would be scraped and not of
all.
Prometheus has a service discovery functionality for deployments running
in Kubernetes. This is now used, when monitoring a Gerrit instance in
Kubernetes. This allows to have a variable number of replicas running,
which will be automatically discovered by Prometheus.
The dashboards were adapted accordingly and allow now to select the
replica to be observed. For now, no summary of all replicas can be
displayed in the dashboards, but that feature is planned to be added
in the future.
Change-Id: I96efc63a192cd90f5e3e91a53dace8e1ae83132e
66 lines
1.1 KiB
YAML
66 lines
1.1 KiB
YAML
gerritServers:
|
|
kubernetes:
|
|
- namespace: default
|
|
label:
|
|
name: app
|
|
value: gerrit-slave
|
|
containerName: gerrit-slave
|
|
port: 8080
|
|
username: admin
|
|
password: secret
|
|
other:
|
|
- host: gerrit.example.com
|
|
username: admin
|
|
password: secret
|
|
promtail:
|
|
storagePath: /var/promtail
|
|
logPath: /var/gerrit/logs
|
|
namespace: namespace
|
|
tls:
|
|
skipVerify: true
|
|
caCert:
|
|
prometheus:
|
|
server:
|
|
host: prometheus.example.com
|
|
username:
|
|
password:
|
|
tls:
|
|
cert:
|
|
key:
|
|
alertmanager:
|
|
slack:
|
|
apiUrl: https://hooks.slack.com/services/xxx/xxx
|
|
channel: '#alerts'
|
|
loki:
|
|
host: loki.example.com
|
|
username:
|
|
password:
|
|
s3:
|
|
protocol: https
|
|
host: s3.eu-de-1.example.com
|
|
accessToken: abcd
|
|
secret: "1234"
|
|
bucket: bucket
|
|
region: eu-de-1
|
|
tls:
|
|
cert:
|
|
key:
|
|
grafana:
|
|
host: grafana.example.com
|
|
tls:
|
|
cert:
|
|
key:
|
|
admin:
|
|
username: admin
|
|
password: secret
|
|
ldap:
|
|
enabled: false
|
|
host:
|
|
port: ""
|
|
password:
|
|
bind_dn:
|
|
accountBases: "[]"
|
|
groupBases: "[]"
|
|
dashboards:
|
|
editable: false
|