Logging & Monitoring for Production
Two hands-on days making a running service explain itself - structured logs a machine can query, metrics that answer a question, traces that find the slow call, and alerts that are worth waking up for. You leave having diagnosed a live incident from the evidence alone.
- Fee
- ₹2,700
- Duration
- 2 days · 16 hours
- Each day
- 09:00 - 17:00
- Mode
- Offline / Online
Designed for
- Developers whose only production tool is a log file they grep
- Engineers who have been asked why a request was slow and could not say
- Teams taking on the operation of what they build
What to bring
- A laptop with Java, Docker and an IDE installed
- A working REST API in any framework
- Basic command-line comfort
What you walk away with
A service emitting structured logs, useful metrics and end-to-end traces into a running observability stack - plus one alert you wrote, tested by causing the condition it watches.
Outcomes
What you will be able to do
- 01Write a log line that a machine can query and a human can read
- 02Attach a correlation identifier that survives a service boundary
- 03Choose a log level for a reason rather than by habit
- 04Read a distributed trace and name the span responsible for latency
View all 9 outcomes
- Instrument a counter, a gauge and a histogram, and know which answers which question
- Distinguish the four golden signals from the metrics nobody looks at
- Write an alert on symptoms rather than causes
- Diagnose an unfamiliar failure from logs, metrics and traces alone
- Keep personal data out of an observability pipeline
The two days
8 hands-on sessions
2 days · 16 hours
- Foundation
- Intermediate
- Advanced
FoundationDay 1 - 09:00 - 10:30
Why the log file stopped working
- logs as text against logs as data
- structured logging with JSON
- what belongs in a log line and what never does
- log levels used deliberately
- sampling and volume as a cost
- the request you cannot find in a million lines
What you will build
An unstructured log converted to structured output, then queried for a condition that was previously ungreppable.
Module 1
FoundationDay 1 - 09:00 - 10:30
Why the log file stopped working
- logs as text against logs as data
- structured logging with JSON
- what belongs in a log line and what never does
- log levels used deliberately
- sampling and volume as a cost
- the request you cannot find in a million lines
What you will build
An unstructured log converted to structured output, then queried for a condition that was previously ungreppable.
Module 1
Book this workshop
This workshop runs on request, for individuals and for teams. Tell us the dates that would suit you.
Running this for a team?