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.

Sign up for GitHub

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

Jump to bottom

High cardinality of Prometheus metrics in self-scrape scenarios (only self-deploy). #725

Open
bwplotka opened this issue Dec 19, 2023 · 1 comment
Open

High cardinality of Prometheus metrics in self-scrape scenarios (only self-deploy). #725

bwplotka opened this issue Dec 19, 2023 · 1 comment
Assignees
@bwplotka
Labels
bug Something isn't working

Comments

@bwplotka
Copy link
Collaborator

The way we configure scrape jobs causes bit high cardinality of net_conntrack_dialer_conn_failed_total. It would be nice to work with the upstream to provide an option to disable it, or improve our example PodMonitoring for self-scrape to explictly ignore this metric.

image
@bwplotka bwplotka added the bug Something isn't working label Dec 19, 2023
@bwplotka
Copy link
Collaborator Author

All metrics with scrape_job has the same issue e.g. prometheus_target_sync_length_seconds but they might have some value for some advanced debugging cases.

https://github.com/prometheus/prometheus/blob/bfbb13cf369da4cd1b29ee52c396c902723febfb/scrape/metrics.go#L138

@maxamins maxamins mentioned this issue Jan 29, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bwplotka bwplotka

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bwplotka