Open murand78 opened 1 year ago
On monolithic setups try with this config
loki:
read:
extraVolumeMounts:
- name: rules
mountPath: "/var/loki/rulestorage/fake"
extraVolumes:
- name: rules
configMap:
name: loki-alerting-rules
This will mount the data from the ConfigMap we created into the pods at /var/loki/rulestorage/fake in a file named rules.yaml. The reason fake is in the path is that this is the instance ID when running in single-tenancy mode. The docs for Loki do not explain this at all but it will not work without that in the path.
Describe the bug Loki alarms not triggered to alertmanager with Monolitic Installation and StorageType filesystem
To Reproduce Install loki 2.8 with helm chart version 5.15.0 and following values.yaml
ConfigMap configured for test alerts:
Expected behavior An alert is sent to the alertmanager. Looking at loki-loggin-0 pod logs the query is correctly executed but the call to the alertmanager is not triggered. This is test query and exploring loki logs the metric is always above this threshold, the alert shall always firing. If I broke the alertmanager config with an Invalid URL no error message are displayed on logs.
Switching the storage type to s3 with ( minio ) all works fine, the alert is correctly sent to the alertmanager updating the values with:
Also the the installation with Simple scalable deployment mode works fine as expected.
Environment:
Screenshots, Promtail config, or terminal output If applicable, add any output to help explain your problem.
LOGS from loki-logging-0 with filesystem storage: ( not firing alerts )
LOGS from loki-logging-0 with s3 storage: ( firing alert )