-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loki data loss #430
Comments
Loki needs a minute to start up. If logs had been sent during that first minute from the fluentd plugin, those logs will not have been stored and therefore cannot be lost. If your apps didnt produce any log output after that, Loki has nothing to receive, and hence will have no labels stored. When your app started sending logs again, labels for those logs started showing up. This is intended behavior. |
@davkal It was not the case. I had started Loki, sent logs to Loki successfully (I can view it on Grafana). But when I came back after a while, data was lost and cannot view from Grafana or via Loki HTTP API. After new logs were sent, the old logs data appear again, only parts of the old labels were lost |
Close issue due to duplicate with #271 |
Labels vanishing after a period of inactivity may be because of #453, which was recently fixed. |
Describe the bug
After Loki started for around 30m~45m without new logs, the data for labels seem to be lost.
Grafana show
Error connecting to datasource: Data source connected, but no labels received. Verify that Loki and Promtail is configured properly.
Query via Loki http api returned empty label list
Send new log to Loki, previous log show up but label only partially restored
To Reproduce
Steps to reproduce the behavior:
sha256:3727574aa6d168f38e25baaed88c70c1bdcbcdd907905c7971a1f8c7e3f94dda
)sha256:6c77ccf94aaf8eb95fa25163da7f93b8eee8dec1a21593d51f742cd169e3daf6
)Expected behavior
Labels are persisted
Environment:
Screenshots, promtail config, or terminal output
docker-compose
loki config
fluentd config
The text was updated successfully, but these errors were encountered: