0bdb1d02e0
So far the install-script could only create a single promtail config.
Since the monitoring setup is able to monitor multiple Gerrit servers,
this caused manual work to create a promtail config per Gerrit server.
Now ytt will create a configuration for each Gerrit host configured
in the config.yaml. Ytt is only able to do that in a single file. Thus,
csplit is used to split the files into separate files that can then
be used to configure promtail on the respective hosts. The config-
files can then be found under
$OUTPUT/promtail/promtail-$GERRIT_HOSTNAME.yaml.
Change-Id: Ib09fba83d8a8fbd45b42e9e5388a85a37ab1a952
56 lines
929 B
YAML
56 lines
929 B
YAML
gerritServers:
|
|
- 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
|