Cardinality in Metrics — Vocabulary and Discussion
Learn vocabulary for discussing metric cardinality, label design, and observability costs.
0 / 10 completed
1 / 10
What is 'cardinality' in the context of metrics?
Cardinality is the number of unique label value combinations for a metric. High cardinality (e.g., a label that contains user IDs) creates millions of time series, causing storage and performance problems.
2 / 10
What is 'label explosion'?
Label explosion occurs when a high-cardinality value (like user ID, session ID, or request path with parameters) is used as a Prometheus label, multiplying time series into millions.
3 / 10
Which is an example of a HIGH cardinality label?
user_id has millions of unique values — one time series per user. This is high cardinality and should not be used as a Prometheus label. The others have low, bounded cardinality.
4 / 10
What does 'metric lifecycle management' mean?
Metric lifecycle management includes identifying unused or redundant metrics, deprecating them, and removing them from instrumentation to reduce storage costs and simplify dashboards.
5 / 10
What is 'exemplar' in OpenTelemetry and Prometheus?
An exemplar is a trace ID (or other reference) attached to a histogram bucket data point, enabling the jump from a metric spike to the specific trace that caused it.
6 / 10
Sarah from the Performance Team commented on your recent PR:
"I'm seeing a huge spike in the 'error_code' metric. The cardinality of that label is incredibly high – we have over 50 distinct error codes being logged, and many are only appearing sporadically. This makes it almost impossible to effectively troubleshoot."
The question tests understanding of how high cardinality impacts metric analysis. Sarah's comment accurately points out that a large number of distinct labels makes it difficult to identify trends or anomalies. The correct answer focuses on the *problem* caused by high cardinality – difficulty in troubleshooting and analysis – rather than simply stating the definition.
7 / 10
You're drafting a PR description for a new feature that introduces a complex user segmentation metric. You want to clearly communicate the potential impact on downstream systems. Which of the following phrases best describes a key aspect of cardinality in this context?
'The number of unique user groups we're tracking is increasing exponentially, potentially overwhelming our data pipelines.'
The question assesses understanding of how cardinality relates to system resource constraints. While security is important, the primary concern with high cardinality in metrics is its impact on data pipelines and storage. The correct answer directly addresses this by focusing on schema optimization – a core strategy for managing cardinality.
8 / 10
During a standup meeting, Ben asks: 'How are we tracking user engagement with the new API?'. You respond:
'We're monitoring the `request_method` and `user_id` labels. The cardinality of those labels is quite high – thousands of unique users are accessing the API daily, but we're seeing a lot of variation in the `request_method`.'
This question tests how to explain cardinality in a non-technical context. The response correctly frames high cardinality as an observation about variation within existing labels, not necessarily a problem *in itself*. It sets the stage for further investigation into the distribution of `request_method`.
9 / 10
You receive an API response from a monitoring service:
{"metric":"error_rate", "label_counts": {"user_segment": 12345, "device_type": 67890, "request_path": 1000}}",
Which of the following statements best describes a concern related to this response?
'The `user_segment` label has a very high count, potentially indicating a problem with user behavior.'
This scenario tests the ability to interpret an API response in terms of cardinality implications. The high count of `user_segment` *could* be a problem – it's worth investigating if it's causing performance issues or skewing analysis. The key is understanding that high cardinality can have downstream effects.
10 / 10
You are configuring OpenTelemetry and Prometheus. You've identified an 'exemplar' trace ID. What does this term primarily represent?
'A single, representative trace instance used for benchmarking performance metrics.'
The term 'exemplar' in OpenTelemetry refers to a single trace used as a baseline. It's a representative instance that allows you to establish normal performance characteristics and identify deviations – essentially, it's a reference point for anomaly detection. This is different from simply tracking the most frequent traces.
What will I practise in "Cardinality in Metrics — Vocabulary and Discussion"?
This module focuses on Observability Engineering — real workplace phrasing you'll use on the job. It contains 10 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 10 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Observability Engineering exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around observability engineering — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Observability Engineering exercises?
See the Observability Engineering hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.