chore(telemetry): add telemetry for metrics query type and count prom… #5627
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…e span metrics alerts
We added the
spanmetrics/delta
pipeline because it's efficient at querying and reduces the memory needed for the collector. To remain backward compatible we kept thespanmetrics/cumulative
pipeline. We have seen delta working well for long enough now. I want to remove the cumulative pipeline for everyone. Before I do that I plan to get an idea of who is using prom alerts based on span metrics, as removing the cumulative pipeline makes alerts not work correctly.See thread for some more context https://signoz-team.slack.com/archives/C06045Z9163/p1722405396987279?thread_ts=1722354481.521489&cid=C06045Z9163