Skip to content
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

Time range ignored #12

Closed
TertiumOrganum1 opened this issue Mar 10, 2024 · 3 comments
Closed

Time range ignored #12

TertiumOrganum1 opened this issue Mar 10, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@TertiumOrganum1
Copy link

Sometimes source refused to take time range into account, especially when specify particular range boundaries (not 'now'). Behavior remain even after ctrl+shift+r.
I found a correlation - this happens when I specify time values as From and To and add non-msg field in query:
_stream:{service=gateway,level=error,status=408} ingest_timestamp:*

image

@Loori-R Loori-R added the bug Something isn't working label Mar 10, 2024
@Loori-R Loori-R self-assigned this Mar 10, 2024
@Loori-R
Copy link
Contributor

Loori-R commented Mar 10, 2024

Hi @TertiumOrganum1, could you wrap the query in (...) and check if the time filter is applied correctly to ensure the issue is related to VictoriaMetrics/VictoriaMetrics#5920:
(_stream:{service=gateway,level=error,status=408} ingest_timestamp:*)

@TertiumOrganum1
Copy link
Author

TertiumOrganum1 commented Mar 11, 2024 via email

@dmitryk-dk
Copy link
Contributor

This bug has been fixed in v0.2.0 release. Closing the issue as fixed then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants