-
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
Logs don't show up unless I expand the window (experimental bolt-db setup) #2700
Labels
stale
A stale issue or PR that will automatically be closed.
Comments
We're also using the experimental bolt-db stuff... |
silverbp
changed the title
Logs don't show up unless I expand the window
Logs don't show up unless I expand the window (experimental bolt-db setup)
Oct 1, 2020
This issue has been automatically marked as stale because it has not had any activity in the past 30 days. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
cyriltovena
pushed a commit
to cyriltovena/loki
that referenced
this issue
Jun 11, 2021
) * Fix Redis cache error when a query has no chunks to lookup Signed-off-by: Marco Pracucci <marco@pracucci.com> * Added CHANGELOG entry Signed-off-by: Marco Pracucci <marco@pracucci.com> * Fixed another case leading to 'wrong number of arguments for 'mget' command' Signed-off-by: Marco Pracucci <marco@pracucci.com>
cyriltovena
added a commit
to cyriltovena/loki
that referenced
this issue
Jun 11, 2021
* Fixes an issue in the index chunks/series intersect code. This was introduce in grafana#2700, more specifically this line https://github.com/cortexproject/cortex/pull/2700/files#diff-10bca0f4f31a2ca1edc507d0289b143dR537 This causes any query with the first label matcher not matching anything to return all matches of all other labels. This is a nasty one since, the code was relying on empty slice, and so it would skip nil values instead of returning no matches. I've added a regression test proving this is fixed everywhere. I think in cortex it can probably affect performance (since you have to download all chunk not required) but not read integrity. I have found this with @slim-bean while deploying Loki, all queriers where OOMing because of this. Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com> * Update changelog. Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com>
cyriltovena
added a commit
to cyriltovena/loki
that referenced
this issue
Jun 11, 2021
* Fixes an issue in the index chunks/series intersect code. This was introduce in grafana#2700, more specifically this line https://github.com/cortexproject/cortex/pull/2700/files#diff-10bca0f4f31a2ca1edc507d0289b143dR537 This causes any query with the first label matcher not matching anything to return all matches of all other labels. This is a nasty one since, the code was relying on empty slice, and so it would skip nil values instead of returning no matches. I've added a regression test proving this is fixed everywhere. I think in cortex it can probably affect performance (since you have to download all chunk not required) but not read integrity. I have found this with @slim-bean while deploying Loki, all queriers where OOMing because of this. Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com> * Update changelog. Signed-off-by: Cyril Tovena <cyril.tovena@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I execute the following log query (you can replicate this behavior in Grafana as well,
logcli query '{job="una-int-current/aurorab"}' --limit=10 --from=2020-09-29T16:10:00-04:00 --to=2020-09-29T17:10:00-04:00
I get no logs.But if I expand the --to by adding one hour to it..
logcli query '{job="una-int-current/aurorab"}' --limit=10 --from=2020-09-29T16:10:00-04:00 --to=2020-09-29T18:10:00-04:00
I get logs that are in the first query window..
2020-09-29T15:39:59-05:00 {} 2020-09-29T16:39:59.351-04:00
If I do --forward, I get logs at the 16:10-04:00 as well.
I've also seen behavior where I've had to expand the
to
get all the logs even though the logs are ALL in the initial window I'm querying, setting the limit to higher didn't help.We are running loki in an eks cluster and are using the helm chart to install it. The following is the values.yaml file that we are using to configure loki
The text was updated successfully, but these errors were encountered: