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

[chore] Update default metric_relabel_configs for internal metrics #5918

Merged
merged 1 commit into from
Feb 18, 2025

Conversation

dmitryax
Copy link
Contributor

The gRPC and HTTP metrics are now only sent at the detailed level. So, no need to exclude them anymore. However, there is another redundant metric emitted by default in 0.119.0 after the transition to OTel SDK, promhttp_metric_handler_errors. This change updates the default configs and the appropriate converter to exclude this metric.

@dmitryax dmitryax requested review from a team as code owners February 17, 2025 23:57
@dmitryax dmitryax force-pushed the exlude-redundant-metrics branch from f464643 to 6d1a614 Compare February 18, 2025 00:10
grpc and http metrics are now only sent in detailed level. So, no need to exclude them. However, there is another redundant metric emitted by default in 0.119.0 after the transition to OTel SDK, `promhttp_metric_handler_errors`. This change updates the default configs and the appropriate converter to exclude this metric.
@dmitryax dmitryax force-pushed the exlude-redundant-metrics branch from 6d1a614 to 70fe718 Compare February 18, 2025 00:52
Copy link
Contributor

@crobert-1 crobert-1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The logic change generally make sense to me, should be good once tests are passing.

@dmitryax dmitryax merged commit 6a16261 into main Feb 18, 2025
257 of 260 checks passed
@dmitryax dmitryax deleted the exlude-redundant-metrics branch February 18, 2025 03:24
@github-actions github-actions bot locked and limited conversation to collaborators Feb 18, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants