Which of the following metrics is unsuitable for a Prometheus setup?
The metric user_last_login_timestamp_seconds{email='john.doe@example.com'} is unsuitable for Prometheus because it includes a high-cardinality label (email). Each unique email address would generate a separate time series, potentially numbering in the millions, which severely impacts Prometheus performance and memory usage.
Prometheus is optimized for low- to medium-cardinality metrics that represent system-wide behavior rather than per-user data. High-cardinality metrics cause data explosion, complicating queries and overwhelming the storage engine.
By contrast, the other metrics---prometheus_engine_query_log_enabled, promhttp_metric_handler_requests_total{code='500'}, and http_response_total{handler='static/*filepath'}---adhere to Prometheus best practices. They represent operational or service-level metrics with limited, manageable label value sets.
Extracted and verified from Prometheus documentation -- Metric and Label Naming Best Practices, Cardinality Management, and Anti-Patterns for Metric Design sections.
Merrilee
11 days agoAnjelica
17 days agoCarmelina
22 days agoDaron
27 days agoPaz
1 month agoMee
1 month agoDahlia
1 month agoLaurene
2 months agoAnthony
2 months agoSylvia
2 months agoBrynn
2 months agoBarbra
2 months agoHerman
2 months agoWillard
3 months agoElza
3 months agoGalen
4 months agoTesha
5 months agoOren
5 months agoTy
5 months agoRebbecca
5 months agoDan
6 months ago