You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we are not collecting metrics that are not enabled for top n queries, which causes certain measurements fields missing in local index sometimes. This is not a consistent behavior, idealy, when user configure "enabling/disabling top n queries by cpu", we should really just adding/removing the logic to push the records into the cpu metric heap, but whether the the top n queries are configured or not, we should always collect the metric.
How can one reproduce the bug?
Enable top n queries by latency only
Enable local index exporter
Wait untail the exporter exports to local index
Enable top n queries by memory or cpu
try to get historical top n queries with from and to
What is the expected behavior?
No error should be thrown and we should always collect the metrics
What is your host/environment?
Operating system, version.
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered:
What is the bug?
Currently we are not collecting metrics that are not enabled for top n queries, which causes certain measurements fields missing in local index sometimes. This is not a consistent behavior, idealy, when user configure "enabling/disabling top n queries by cpu", we should really just adding/removing the logic to push the records into the cpu metric heap, but whether the the top n queries are configured or not, we should always
collect
the metric.How can one reproduce the bug?
from
andto
What is the expected behavior?
No error should be thrown and we should always collect the metrics
What is your host/environment?
Operating system, version.
Do you have any screenshots?
If applicable, add screenshots to help explain your problem.
Do you have any additional context?
Add any other context about the problem.
The text was updated successfully, but these errors were encountered: