Practice log analysis vocabulary: searching recent errors, identifying error spikes with timestamps, saved searches, dashboard log volume, and correlating errors with deployments.
0 / 17 completed
1 / 17
During triage an engineer runs a query: 'Show me all ___ in the last 30 minutes.' What are they searching for?
'Searching for errors in the last 30 minutes' is a standard first step in incident triage — filtering the log aggregator to show only error-level entries within the incident window to understand what is failing and where.
2 / 17
The incident timeline notes: 'The ___ in 500s started at 14:32.' What pattern are they describing?
A spike in 500 errors is a sudden increase in HTTP 500 (Internal Server Error) responses. Identifying the exact start time (14:32) is critical for correlating the spike with a deployment, configuration change, or infrastructure event.
3 / 17
The team creates a ___ search for the authentication error pattern so they can reuse it during future incidents.
A saved search in a log aggregator (Kibana, Grafana, Splunk) stores a query — filters, field selections, and time range settings — so it can be executed instantly. Saving common investigation queries reduces mean time to resolution during incidents.
4 / 17
The ___ dashboard shows log volume by service, making it easy to see which service is generating the most noise.
A log volume dashboard charts the number of log entries (or error entries) per service over time. Unusual spikes in log volume from a specific service are often the first visible symptom of an incident before alerts fire.
5 / 17
Post-incident analysis shows: 'The error ___ with deployment X.' What does this finding mean?
'The error correlates with deployment X' means the spike in errors began at the same time as a specific deployment, making that deployment the prime suspect for the root cause. Correlation does not prove causation — but it focuses the investigation.
6 / 17
Sarah, a SRE, is reviewing a code change that introduces a new feature. She sees the following log entry in the application logs: 'ERROR: Failed to serialize request body - JSONDecodeError'. What does this log message likely indicate?
This message signifies a parsing error. JSONDecodeError specifically points to a problem with the data format being sent—likely an invalid JSON structure or improperly encoded characters. It's crucial to investigate the client-side code sending the request for potential issues.
7 / 17
David, a developer, is investigating a spike in error logs related to API calls. He uses Kibana and performs a query: 'duration > 10ms AND service == "payment_processing"'. What kind of analysis is David conducting?
David is using Kibana's filtering capabilities to identify slow API calls. The query focuses on duration exceeding a threshold (10ms) and specifies the service ('payment_processing') to narrow down the scope and diagnose performance problems within that specific area.
8 / 17
During incident response, a monitoring system alerts: 'High frequency of 404 errors for /api/v1/users'. The on-call engineer notes this in the incident timeline as '404s in 500s started at 14:32.' What pattern is being described?
The phrase '404s in 500s' denotes a recurring pattern – specifically, a high frequency of 404 errors happening repeatedly within a defined timeframe (indicated by the timestamp). This suggests an ongoing issue with resource availability or routing configuration related to the specified API endpoint.
9 / 17
Maria, a DevOps engineer, is creating a Slack message for her team to notify them of an anomaly. She writes: 'High volume of error logs in the web server - investigating'. What type of log data is Maria referring to?
Maria's message highlights 'error logs', which are typically verbose messages detailing issues encountered within an application. This indicates a significant increase in the volume of these messages, suggesting something is going wrong with the web server's operations.
10 / 17
John, a developer, is troubleshooting a slow API response. He examines the logs and notices frequent entries related to 'timeouts'. In a Slack message to his team, he writes: 'We're seeing high latency with requests hitting the payment_processing service – lots of timeout errors.' What does 'timeout' likely indicate in this context?
'Timeout' errors signify that an API call didn't receive a response within a defined timeframe. This often points to issues like slow processing on the server-side or network problems preventing timely communication – it doesn't necessarily mean the server is overloaded (though that could be a contributing factor). Option A represents a common, but less precise, interpretation.
11 / 17
Emily, an SRE, is reviewing a pull request for a new feature. The code includes logging that reads: 'WARN: Failed to connect to external service AuthService – connection timeout'. What does this log message suggest about the application's behavior?
A 'connection timeout' log entry indicates that the application attempted to connect to AuthService but didn't receive a response within an expected time. This suggests a problem with the connection itself—the service might be unavailable or there could be network issues preventing communication. Options C and D are less likely interpretations based on this specific message.
12 / 17
Ben, a DevOps engineer, is monitoring application logs using a dashboard. He notices a consistently high number of entries labeled: 'ERROR: Invalid JSON payload received'. What does this message suggest about the data being processed by the application?
An 'Invalid JSON payload' error means the data received by the application wasn't formatted correctly according to what it expected. This often happens when APIs return incorrect or malformed data – a fundamental issue in data processing. Option D is possible but less likely without additional context.
13 / 17
During a post-incident review of a database outage, the team notes: 'The `slow_query` metric spiked dramatically around 09:00.' What is the primary meaning of this statement in the context of log analysis?
'Slow_query' is a metric often used to identify long-running or inefficient queries within log data. This statement indicates that a specific query was causing performance issues, likely consuming significant resources and contributing to the outage. It doesn't imply hardware failure or network problems; instead, it focuses on inefficient database activity.
14 / 17
Liam, a developer, is investigating intermittent errors in a microservice. He observes the following log entry repeatedly: `[ERROR] Connection refused - Address '192.168.1.100', Port 8080`. What does this message most likely indicate?
This log message signifies a classic connection refusal error. The `Connection refused` indicates that the client attempted to establish a connection but received no response from the server at the specified address and port, meaning the service wasn't reachable or listening on that port. This is distinct from firewall issues or DNS problems.
15 / 17
During a Slack discussion about a recent performance issue, Maya, a DevOps engineer, writes: 'We're seeing a high volume of `4XX` errors in the access logs – specifically, 404s and 419s.' What does Maya's message suggest about potential problems?
High volumes of `4XX` errors (client errors) often point to issues with URLs or resource availability. Specifically, 404s indicate missing resources and 419s usually relate to broken links or redirects. This suggests a problem with the client's requests rather than server-side issues like authentication or overload.
16 / 17
In a code review comment, David notes: 'The log entry `WARN: Failed to serialize request body - JSONDecodeError` suggests a problem with the data being sent to the API.' What is the underlying cause of this error?
A `JSONDecodeError` arises when the data received by the server isn't valid JSON. This means the client is sending a string that doesn't conform to the expected JSON syntax – this is a common cause of API integration problems and not related to network issues or server overload.
17 / 17
Sarah, an SRE, is investigating alerts from a monitoring system. The alert states: 'High frequency of `503 Service Unavailable` errors originating from the order processing service.' What does this message indicate about the order processing service's health?
'503 Service Unavailable' errors signify that the service is temporarily unable to handle new requests. This could be due to resource constraints (CPU, memory) or issues with dependent services – essentially, the service is overwhelmed and can't fulfill requests at the moment.
What will I practise in "Log Analysis Vocabulary"?
Practice log analysis vocabulary: searching recent errors, identifying error spikes with timestamps, saved searches, dashboard log volume, and correlating errors with deployments.
How many exercises are in this module?
This module has 17 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.