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

fix the calculation of incremental-sum #15468

Merged
merged 2 commits into from Jul 20, 2023

Conversation

ktsaou
Copy link
Member

@ktsaou ktsaou commented Jul 20, 2023

  • when calculating incremental sum, if the data have flat steps, the calculation was missing the delta
  • when planning the query to select the right tier, assume the minimum required is 400 points, to pick the tier that will provide at least this resolution. This should improve the precision of metrics correlations, anomaly advisor, badges and alerts.

@ktsaou
Copy link
Member Author

ktsaou commented Jul 20, 2023

@andrewm4894 the second bullet should fix the issue with the precision metrics correlations and anomaly rate that ask for 1 points. So, now the query planner will try to find a tier that can provide around 400 points for the time-frame requests and selected the one that is closer to 400.

@ktsaou ktsaou merged commit d36fb28 into netdata:master Jul 20, 2023
133 of 134 checks passed
stelfrag pushed a commit to stelfrag/netdata that referenced this pull request Aug 1, 2023
* fix the calculation of incremental-sum

* for query planning use at least 400 points

(cherry picked from commit d36fb28)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant