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-series aggregation step in diff / comparison queries #3587

Open
kolesnikovae opened this issue Sep 24, 2024 · 0 comments
Open

Time-series aggregation step in diff / comparison queries #3587

kolesnikovae opened this issue Sep 24, 2024 · 0 comments
Labels
type/bug Something isn't working ux

Comments

@kolesnikovae
Copy link
Collaborator

The time series always uses sum aggregation, and the aggregation window depends on the time range.

For example, when you query the last hour, each point represents the sum of values within a 5-second window. However, when you query the last 12 hours, the window increases to 30 seconds, so each point covers a larger time span and aggregates more data. This results in higher sums for each point, which can be misleading if you're expecting consistent, time-normalized values across different time ranges.

That said, I find this behavior quite confusing. I believe users expect to see series where the values are normalized across different time windows. This inconsistency feels like a bug, and I think we should fix it to provide more intuitive results.

In the screenshot below you can see that in the diff view, the difference is even more pronounced and confusing:

Image

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

No branches or pull requests

1 participant