-
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
Log message sometimes returned and sometimes not #2668
Comments
Hi, Would that have any similarity with this issue? On my case I got no data when I provide certain intervals (1s I get data, 100ms I do not get)... BR |
It could be, but sounds slightly different. I can run the exact same query, and sometimes get results and sometimes not. It doesn't seem to just be a problem when returning log messages of a large size, even smaller sized log messages go missing |
The problem for us was #2624 |
OK. |
* do not invalidate chunks cache when series are deleted Signed-off-by: Sandeep Sukhani <[email protected]> * add comment regarding exclusion of chunksCache from invalidating cache for series deletion Signed-off-by: Sandeep Sukhani <[email protected]>
Run into same issue.
|
Describe the bug
We were running a search in Grafana explorer and sometimes would find a log entry and on other occasions it would not. I've since moved to using the logcli and can produce the same results (ruling out grafana), we were running 1.3.0 of Loki (where we feel like the message would disappear completely once moving out of memory and into GCS backed storage), I’ve since upgraded everything to 1.6.1 Loki (we use the docker image) and a similar problem still occurs, where the log message will sometimes be returned and other times not, without changing query or start/end times. We’re currently running Loki in single binary mode, but don’t have lots of logs in this staging environment (same problem occurs in production environment as well, which is separate Loki set-up etc)
I've not found anything obvious in the Loki logs themselves (in debug mode) as to why this might be happening.
To Reproduce
Steps to reproduce the behavior:
go/bin/logcli --addr=http://XX:3100 query --stats --from="2020-09-24T13:00:00Z" --to="2020-09-24T15:00:00Z" '{appName="XX"} |= "uniqueIdForTheSpecificLogEntry"'
Expected behavior
Every time we execute the query, the same result set is returned. It seems completely random as to whether the entry will be returned or not.
Environment:
- Promtail is manually edited YAML and deployed as daemonSet
- Loki is run on a single server not in K8s but running Docker with command for the container
/usr/bin/loki -config.file=/etc/loki/loki-config.yaml -log.level=debug
Screenshots, Promtail config, or terminal output
If applicable, add any output to help explain your problem.
Loki Config (/etc/loki/loki-config.yaml):
logcli Output, run the command it finds and returns the log entry, run the command again right after and get no log entry returned:
The text was updated successfully, but these errors were encountered: