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

rule: expression with max_over_time no return data #8001

Open
ximito opened this issue Dec 17, 2024 · 2 comments
Open

rule: expression with max_over_time no return data #8001

ximito opened this issue Dec 17, 2024 · 2 comments

Comments

@ximito
Copy link

ximito commented Dec 17, 2024

Prometheus and Golang version used:
Thanos 0.36.1

Object Storage Provider: None

What happened:

I'm using the rule component. I have defined an expression where the "max_over_time" function is used. In the evaluation time of the rule, nothing is returned, and no information is returned in the log either. But this expression returns data correctly from Thanos Query.

What you expected to happen:
Return the same value like a Thanos query

Copy link

dosubot bot commented Dec 17, 2024

Hey @ximito, I'm here to help you with any bugs, questions, or contributions you have. Let's get that issue sorted for you!

The issue you're experiencing with the max_over_time function in the Thanos rule component not returning data, while it works in Thanos Query, could be due to several factors:

  1. Evaluation Failures: Ensure that the rule expression is correctly defined and that there are no evaluation failures. Check for any alerts like ThanosRuleHighRuleEvaluationFailures that might indicate issues with the query API endpoint used [1].

  2. Configuration Issues: Verify that the Thanos rule component is correctly configured with the necessary query URLs and rule files. Ensure that the --grpc-query-endpoint is correctly set to point to the Thanos Query component [2].

  3. Logging Configuration: Since no information is returned in the log, consider adjusting the logging level to DEBUG to capture more detailed logs. This can help identify any underlying issues during rule evaluation [3].

  4. Query Reliability: The Thanos rule component relies on the Thanos Query component for data. Ensure that the query endpoints are reliable and accessible. Any network issues or DNS failures could prevent data from being fetched [1].

  5. Time Series Data Handling: There might be differences in how the rule component handles time series data compared to the query component. Ensure that the data is available and correctly queried by the rule component.

By checking these aspects, you should be able to diagnose and resolve the issue with the max_over_time function in your Thanos rule expression.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@AgustinICAI
Copy link

I can ensure that happens, that Thanos ruler 0.36.1 is not able to evaluate functions with range-vectors, although thanos query is able to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants