Practice the vocabulary for reading and communicating about monitoring dashboards: metrics, graphs, anomaly detection, and alert thresholds.
0 / 13 completed
1 / 13
What does a 'spike' on a monitoring graph typically indicate?
Spikes are short-lived anomalies. They may be normal (cron job running, batch import) or concerning (error rate spike, memory pressure). Context determines significance — a spike on weekdays at 9am is likely expected traffic.
2 / 13
What does 'P99 latency' mean on a dashboard?
P99 shows worst-case latency for most users. Average latency can hide tail performance problems — a P99 of 2 seconds means 1 in 100 requests is very slow. P99 and P95 are the key dashboard metrics for user experience monitoring.
3 / 13
What does 'error rate' on a dashboard represent?
Error rate = errors / total requests * 100%. An error rate of 0.5% might be acceptable; a sudden jump to 5% is a significant incident signal. Absolute error counts are less useful than rates because they depend on traffic volume.
4 / 13
What is a 'saturation' metric in the RED method?
The RED method: Rate, Errors, Duration. The USE method adds Utilization, Saturation, Errors. Saturation metrics predict problems: 95% CPU saturation means the system is near its limit — errors and latency spikes follow if load increases.
5 / 13
What does 'flapping alert' mean in a monitoring context?
Flapping alerts fire and resolve repeatedly, creating alert fatigue. They indicate the threshold is set too close to the normal operating range. Solutions: raise the threshold, use hysteresis (require the metric to stay above threshold for N minutes), or fix the underlying oscillation.
6 / 13
How would you describe a 'heatmap' visualization to a colleague?
Heatmaps (common in Grafana) show latency distributions over time. A bimodal distribution (two color bands) might reveal that some requests are served from cache (fast) and others from the database (slow) — invisible in a simple P99 graph.
7 / 13
What does 'cardinality' mean in the context of monitoring metrics?
High-cardinality labels (user_id, request_id) create millions of unique metric series and can crash Prometheus or dramatically increase costs. Design metrics with controlled cardinality: use status_code, endpoint, region — not unique IDs.
8 / 13
What does 'baseline' mean in anomaly detection on dashboards?
Baselines capture 'normal' — which may vary by time of day, day of week, or season. Dynamic anomaly detection flags when current values deviate significantly from the baseline pattern, rather than fixed thresholds.
9 / 13
During a code review of the new user onboarding service, Sarah points out that the 'Request Latency' graph shows a spike during peak hours. Mark replies: 'Looks like we're experiencing high load.' What is Mark *most likely* referring to when he says this?
Mark's statement focuses on the graph – a spike in 'Request Latency' during peak hours strongly suggests the system is overloaded. While errors, network issues, or code bottlenecks could *cause* latency, Mark is directly observing the symptom of high load and its impact on response times. Option C is less likely as it describes an isolated issue that wouldn't necessarily cause a spike.
10 / 13
You're reviewing the dashboard for the microservice handling order processing. You notice a recurring alert stating 'High CPU Utilization – Service X'. The accompanying data shows that this has been consistently above 85% during business hours. What does this *primarily* indicate?
While inefficient code or malicious attacks could contribute, the 'consistent' nature of high CPU utilization during business hours strongly suggests that the service is legitimately handling an increased workload – i.e., it's doing what it's designed to do under normal circumstances. Option A is too broad; Option D is a possible cause but not the primary indicator from the dashboard data alone. Option B requires more investigation.
11 / 13
In a Slack channel discussing performance issues with a new feature, David says: 'We need to investigate the P95 latency – it's currently exceeding 2 seconds!' What does he specifically mean?
'P95 latency' refers to the 95th percentile of response times – meaning that 95% of all requests to a service or application take *less* than the specified value (in this case, 2 seconds). It's a key metric for understanding the tail-end performance and is often more informative than average latency. Option C describes an error state; Option D relates to SLOs but doesn't directly explain what P95 latency represents.
12 / 13
During a standup meeting, Alex reports: 'The 'Saturation' metric for the database connection pool is consistently at 100% during peak times.' What does this likely signify?
'Saturation' at 100% in a connection pool indicates that all available connections are currently in use. This suggests the application or service is attempting to acquire more connections than the pool's capacity allows, leading to queuing and potential delays – a classic sign of resource contention. While hardware limitations could also be a factor, saturation focuses on the immediate utilization of the pool resources.
13 / 13
You're reviewing a PR that introduces a new feature. The code reviewer comments: 'This could lead to flapping alerts if not properly handled.' What does this comment *most likely* imply?
'Flapping alerts' refer to a situation where an alert triggers frequently, often due to transient conditions or unstable states in the system. The reviewer is warning that the new code might introduce such instability – for example, temporary resource exhaustion leading to brief periods of high load and subsequent alert activation – before resolving itself. This highlights the need for robust error handling and monitoring.
What will I practise in "Reading Monitoring Dashboards (English)"?
Practice the vocabulary for reading and communicating about monitoring dashboards: metrics, graphs, anomaly detection, and alert thresholds.
How many exercises are in this module?
This module has 13 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the vocabulary and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Log Reading exercises?
Browse the full Log Reading hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain vocabulary and concepts in prose; this exercise tests and reinforces that vocabulary through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.