fad4eba966
Gerrit instances that are loadbalanced cannot easily e scraped by
an external Prometheus, since the request won't end up at a specified
Gerrit instance. A typical setup to solve this issue, is to install a
local Prometheus and scrape the local Prometheus from the central
Prometheus. This is a so called federated setup.
Now such a setup is supported and can be configured.
Change-Id: I0119d3c1d846cd8e975e5732f4d59cf863c6d2b8
74 lines
1.3 KiB
YAML
74 lines
1.3 KiB
YAML
gerritServers:
|
|
kubernetes:
|
|
- namespace: default
|
|
label:
|
|
name: app
|
|
value: gerrit-slave
|
|
containerName: gerrit-slave
|
|
port: 8080
|
|
username: admin
|
|
password: secret
|
|
federatedPrometheus:
|
|
- host: prometheus.example.com
|
|
port: 9090
|
|
username: admin
|
|
password: secret
|
|
other:
|
|
- host: gerrit.example.com
|
|
username: admin
|
|
password: secret
|
|
healthcheck: false
|
|
promtail:
|
|
storagePath: /var/promtail
|
|
logPath: /var/gerrit/logs
|
|
namespace: namespace
|
|
tls:
|
|
skipVerify: true
|
|
caCert:
|
|
monitoring:
|
|
prometheus:
|
|
server:
|
|
host: prometheus.example.com
|
|
username:
|
|
password:
|
|
tls:
|
|
cert:
|
|
key:
|
|
alertmanager:
|
|
slack:
|
|
apiUrl: https://hooks.slack.com/services/xxx/xxx
|
|
channel: '#alerts'
|
|
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
|
|
logging:
|
|
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:
|