Learn vocabulary for designing and discussing structured logging systems.
0 / 10 completed
1 / 10
What is 'structured logging'?
Structured logging outputs log entries as machine-readable objects (typically JSON) with consistent fields (timestamp, level, message, service, trace_id, etc.) — enabling efficient querying and analysis.
2 / 10
What is a 'correlation ID' (or trace ID) in logging?
A correlation ID (or trace ID) is added to every log entry generated during a request. It allows all logs — across multiple services — for a single request to be found and correlated.
3 / 10
What is the correct log level for an unexpected error that requires investigation but doesn't stop the service?
ERROR is the correct level for unexpected errors that require investigation but allow the service to continue — as opposed to FATAL (service cannot continue) or WARN (unexpected but handled gracefully).
4 / 10
What is a 'log schema' in structured logging?
A log schema defines the standard fields all log entries must have (e.g., timestamp, level, service, trace_id, message) ensuring consistent structure across services.
5 / 10
What is 'log verbosity' in service configuration?
Log verbosity refers to how much detail is captured. DEBUG captures everything (high verbosity, high cost); ERROR captures only errors (low verbosity, low cost).
6 / 10
Alice: 'I'm seeing a lot of `WARN` logs coming from the authentication service. Should I be concerned, or is this just normal background activity?'
Which response best reflects appropriate guidance regarding structured logging and log levels?
Alice is correctly recognizing that `WARN` logs require investigation, but needs guidance on *how* to investigate effectively. The key is understanding that `WARN` alone isn't enough; the structured log data (correlation ID, timestamp) provides crucial context needed for tracing and diagnosis. Simply stating 'WARN = problem' doesn't leverage the power of structured logging.
7 / 10
Mark is reviewing a pull request that adds a new feature to an e-commerce platform. The PR description includes the following log message:
`{"timestamp": "2024-10-27T10:30:00Z", "level": "INFO", "service": "product_catalog", "message": "Item added successfully", "correlation_id": "a1b2c3d4"}`
What is the primary purpose of including the correlation_id in this log message?
The correlation_id is fundamental to distributed tracing. It allows you to link together logs from multiple services involved in a single user request—crucially enabling debugging and performance analysis when issues occur across systems. Simply knowing an item was added isn't enough; understanding *how* that addition relates to the broader transaction is vital.
8 / 10
You are configuring a new microservice and need to control the amount of logging performed. Which setting would you adjust to reduce the volume of logs generated by this service?
Log verbosity directly controls the granularity of logging. Setting it to 'minimal' (or equivalent) will reduce the number of messages logged by reducing the amount of information captured per event. Increasing the log level changes *what* is logged, not the quantity.
9 / 10
David explains to a junior developer that 'a log schema' is like…
Which of these best describes a log schema?
The log schema defines the *structure* of the logged data – it dictates what fields are present and their expected data types. This is essential for parsing and analyzing logs effectively. A database table or a naming convention doesn't represent this structural definition.
10 / 10
During a stand-up meeting, Sarah reports that the payment processing service is experiencing intermittent failures. The service's configuration includes the following setting: `log_verbosity = 'detailed'`. What impact will this setting have on your team's ability to diagnose and resolve the issue?
Setting `log_verbosity = 'detailed'` results in a high volume of log data. While potentially helpful for debugging, the sheer quantity can overwhelm the system and make it difficult to isolate relevant errors and identify root causes. 'Detailed' logging without proper filtering is often counterproductive.
What will I practise in "Structured Logging — Vocabulary and Language"?
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.