Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Linux Foundation PCA Exam - Topic 1 Question 12 Discussion

Which of the following metrics is unsuitable for a Prometheus setup?
D) user_last_login_timestamp_seconds{email='john.doe@example.com'}
A) prometheus_engine_query_log_enabled
B) promhttp_metric_handler_requests_total{code='500'}
C) http_response_total{handler='static/*filepath'}

Linux Foundation PCA Exam - Topic 1 Question 12 Discussion

Actual exam question for Linux Foundation's PCA exam
Question #: 12
Topic #: 1
[All PCA Questions]

Which of the following metrics is unsuitable for a Prometheus setup?

Show Suggested Answer Hide Answer
Suggested Answer: D

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.

Contribute your Thoughts:

0/2000 characters
Merrilee
11 days ago
Yeah, D should not be in Prometheus.
upvoted 0 times
...
Anjelica
17 days ago
C seems okay, but D is just too personal.
upvoted 0 times
...
Carmelina
22 days ago
A is fine, but D is definitely not a good metric.
upvoted 0 times
...
Daron
27 days ago
I feel like A is also questionable.
upvoted 0 times
...
Paz
1 month ago
Agreed, D doesn't fit well.
upvoted 0 times
...
Mee
1 month ago
I think D is unsuitable. Too specific.
upvoted 0 times
...
Dahlia
1 month ago
D is definitely the odd one out.
upvoted 0 times
...
Laurene
2 months ago
B is useful for tracking errors.
upvoted 0 times
...
Anthony
2 months ago
C seems fine. It's a valid metric.
upvoted 0 times
...
Sylvia
2 months ago
I like A. It's a config option, not a metric.
upvoted 0 times
...
Brynn
2 months ago
Agreed, D doesn't fit well.
upvoted 0 times
...
Barbra
2 months ago
I think D is unsuitable. Too specific.
upvoted 0 times
...
Herman
2 months ago
A is the one that stands out as unsuitable.
upvoted 0 times
...
Willard
3 months ago
B and C are totally valid metrics, no doubt!
upvoted 0 times
...
Elza
3 months ago
Wait, why would D be a problem? Seems fine to me.
upvoted 0 times
...
Galen
4 months ago
I think A is the right answer here!
upvoted 0 times
...
Tesha
5 months ago
D is definitely not suitable for Prometheus.
upvoted 0 times
...
Oren
5 months ago
I’m leaning towards D as well, but I’m not confident. It just seems like it wouldn’t fit the usual metric patterns we discussed.
upvoted 0 times
...
Ty
5 months ago
I feel like I've seen a similar question before, and I think it was about the format of the metrics. Could it be A?
upvoted 0 times
...
Rebbecca
5 months ago
I'm not entirely sure, but I remember something about metrics needing to be aggregated. Maybe option C is the odd one out?
upvoted 0 times
...
Dan
6 months ago
I think option D might be the one that's unsuitable since it seems too specific for Prometheus metrics.
upvoted 0 times
...

Save Cancel