eb4e6ea191
The chunks created by Loki were stored in a persistent volume. This
does not scale well, since volumes cannot easily be resized in
Kubernetes. Also, at least the ext4-filesystem had issues, when large
numbers of logs were saved. These issues are due to the dir_index as
discussed in [1].
An object store provides a more scalable and cheaper solution. Loki
supports S3 as an object storage and also other object stores that
understand the S3 API like Ceph or OpenStack Swift.
[1] https://github.com/grafana/loki/issues/1502
Change-Id: Id55095c3b6659f40708712c1a494753dbcab7686
56 lines
917 B
YAML
56 lines
917 B
YAML
gerritServers:
|
|
- host: gerrit.example.com
|
|
username: admin
|
|
password: secret
|
|
namespace: namespace
|
|
tls:
|
|
skipVerify: true
|
|
caCert:
|
|
promtail:
|
|
storagePath: /var/promtail
|
|
logPath: /var/gerrit/logs
|
|
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
|