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.
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
- Fee
- ₹2,700
- Duration
- 2 days · 16 hours
- Each day
- 09:00 - 17:00
- Mode
- Offline / Online
The 2 days, hour by hour
10 hands-on sessions: every one ends in a thing
Day 1
09:00 - 17:00Logs and metrics that answer questions
5 sessions09:00 – 10:15
Turn a log file into something a machine can query
structured JSON logs into Loki, log levels used deliberately, what never gets logged
Takeaway An unstructured log converted and then queried for a condition that was previously ungreppable.
10:30 – 11:45
Follow one request across two services
correlation IDs, MDC and thread context, logging once per request
Takeaway Every line for one request retrieved in a single query, across a service boundary.
12:00 – 13:00
Instrument metrics that answer a question
Prometheus counters and gauges, histograms and cardinality, the four golden signals
Takeaway A latency histogram with p95 read off it, and a high-cardinality label shown exploding the store.
14:00 – 15:15
Build the one dashboard people actually use
rate errors duration in Grafana, baselines, annotating deploys
Takeaway A dashboard that answers "is it up, is it slow, is it failing" in under ten seconds.
15:30 – 17:00
Trace a slow request across three services
OpenTelemetry spans, sampling, reading a flame graph
Takeaway The responsible span identified in under a minute, end to end.
Day 2
09:00 - 17:00Alerts, deploys and the incident
5 sessions09:00 – 10:15
Write an alert worth waking up for
symptoms vs causes, thresholds and flapping, runbooks
Takeaway One alert written, fired on purpose, and resolved by following its own runbook.
10:30 – 11:45
Deploy without dropping a request
liveness vs readiness, graceful shutdown, draining
Takeaway A restart under load with no failed request, proved by the load generator, not asserted.
12:00 – 13:00
Keep the pipeline legal and affordable
personal data in logs, retention, cost drivers
Takeaway A pipeline checked for personal data, and a retention setting you can defend.
14:00 – 15:15
Diagnose a live incident from evidence alone
symptom to cause, discarding hypotheses
Takeaway An unfamiliar failure worked from logs, metrics and traces to a named cause.
15:30 – 17:00
Write the timeline and close the loop
incident timelines, what instrumentation was missing
Takeaway A written diagnosis, and the list of what you would instrument before the next incident.
By the end of day 2, you are holding
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.
No dates announced
We open batches around demand. Tell us the schedule that would work and we will let you know first.
Send your details instead
More SkillLabs
One weekend, one capability
Agent Builder Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
AI App Engineering Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Ground the Model: RAG Engineering Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Idea to Internet
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Agents in the Wild: Production Agent Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Break It Before Users Do: AI Reliability Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Give Your Agent Hands: MCP Tooling Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Docker & Kubernetes for Developers
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Git, GitHub and GitHub Actions for Developers
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
JavaScript and TypeScript Foundations
5 days · 10 hours
Runs on request
See the plan
Ship It on AWS: Cloud Deployment for Developers
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
SQL for Application Developers
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Events in Motion: Kafka & Messaging for Java Developers
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Linux Command Line Essentials
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Performance & Production Readiness
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Redis & Caching for Java Services
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Secure the Frontend: Authentication & Web Security Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Test It Before You Ship It: Java API Testing Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Test the User Journey: Frontend Testing Lab
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
TypeScript for Application Developers
₹2,700 · 2 days · 16 hours
Runs on request
See the plan
Who runs it
Practitioners, in the room with you
All trainers and mentorsEach workshop names its trainer before you book.

Vishal Shah
Founder & Principal Trainer
Two decades building and teaching commerce, banking and cloud platforms, and still writing code
- Java & Spring Boot microservices
- TypeScript, React, Angular & Next.js
- Composable commerce (commercetools)

Shrenik Shah
Principal Trainer
Cloud and AI architect who has upskilled over 5,000 engineers in Java, React, Python and cloud
- Python: Django, Flask, GenAI & agentic workflows
- Java & Spring Boot
- React & Angular, micro-frontend architecture
Running this for a team?
We deliver SkillLabs on site for institutions and engineering teams.
₹2,700
2 days · 16 hours