You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our Grafana instance is configured to use Loki as a data source:
Yet, if the deployment has been already running for a while, an attempt to read any data from http://loki-headless:3100 may fail:
$ kubectl port-forward svc/loki-headless 3100:3100Forwarding from 127.0.0.1:3100 -> 3100Forwarding from [::1]:3100 -> 3100Handling connection for 3100Handling connection for 3100E1028 19:15:59.198902 1075296 portforward.go:406] an error occurred forwarding 3100 -> 3100: error forwarding port 3100 to pod 2444f44c3633d6be7250dcbe0aa36181a37aaed5433fe380a7616fcb384df8f0, uid : failed to execute portforward in network namespace "/var/run/netns/cni-40f89c3a-8386-d8f6-d6d7-832f0b8fea0e": failed to dial 3100: dial tcp4 127.0.0.1:3100: connect: connection refusedE1028 19:15:59.194892 1075296 portforward.go:406] an error occurred forwarding 3100 -> 3100: error forwarding port 3100 to pod 2444f44c3633d6be7250dcbe0aa36181a37aaed5433fe380a7616fcb384df8f0, uid : failed to execute portforward in network namespace "/var/run/netns/cni-40f89c3a-8386-d8f6-d6d7-832f0b8fea0e": failed to dial 3100: dial tcp4 127.0.0.1:3100: connect: connection refusedE1028 19:15:59.282113 1075296 portforward.go:234] lost connection to pod
This may be caused by the Loki instance having run out of disk space:
$ kubectl exec -it po/save-cloud-loki-0 -- /bin/sh/ $ du -hs /var/loki/chunks9.6G /var/loki/chunks/ $ df -h /var/loki/chunksFilesystem Size Used Available Use% Mounted on/dev/sdb 9.8G 9.8G 0 100% /var/loki
The effective config of the running instance is located at /etc/loki/config/config.yaml. According to the documentation, for a non-default retention, a compactor section needs to be added to the YAML, e.g.:
Our Grafana instance is configured to use Loki as a data source:
Yet, if the deployment has been already running for a while, an attempt to read any data from
http://loki-headless:3100
may fail:This may be caused by the Loki instance having run out of disk space:
The effective config of the running instance is located at
/etc/loki/config/config.yaml
. According to the documentation, for a non-default retention, acompactor
section needs to be added to the YAML, e.g.:The text was updated successfully, but these errors were encountered: