Logging, error handling and observability standards for developers
A ready-made course you customise for your organisation, with a live session deck and two surveys. You only add the 10 details that are specific to your organisation.
- Length
- 35 min
- Lessons
- 6 lessons
- Frequency
- At onboarding, after a hard-to-trace incident
- Last reviewed
- 21 Oct 2026
A handler logs the error and then swallows it, so the caller thinks the payment succeeded
Try it: this is one of 16 interactive activities in the course.
What's included
Three pieces that work together
Copy once, get everything. Learners prepare on their own, you answer questions live, and the surveys tell you what stuck.
Self-paced course
Short lessons with real workplace scenarios, not walls of text.
- 6 lessons, about 35 minutes
- Process, scenario, timeline, accordion and quizzes
Live session deck
An AhaSlides presentation to run after the course, in person or online.
- 10 slides
- Quiz, poll, ranking, word cloud slides
- A closing slide for your contacts
Two surveys
Find out what landed, and whether people use it on the job.
- Post-course feedback, about 2 minutes
- 30-day check-in
- Anonymous by default
- Results feed your next refresher
Learning objectives
At the end of this course, learners can
Each objective and the lesson that covers it.
| ID | Objective | Source | Where it's covered |
|---|---|---|---|
| TO 329.0 | Achieve ≥ 80% on the final assessment | - | Whole course |
| SO 329.1 | Write a log line that a stranger can act on: level, event, identifier and outcome | Best practice; OWASP Logging Cheat Sheet | Whole course |
| SO 329.2 | Name the data that must never reach a log (secrets, full card numbers, personal data) and show how to mask it + your info | ISO/IEC 27002:2022 control 8.15; organisation data policy | Whole course |
| SO 329.3 | Handle an error so the next person can find the cause, without hiding it or leaking detail to users | Best practice | Whole course |
| SO 329.4 | Choose a sensible alert threshold and say who is paged + your info | Best practice | Whole course |
| SO 329.5 | Apply the retention and audit-trail rules of your organisation + your info | ISO/IEC 27002:2022 control 8.15 | Whole course |
Your part: what a template can't do for you
- Your workplace details: fill in the 10 highlighted fields so the course describes your own policies, contacts and locations.
- Records: record completion in your own LMS or record system.
Course outline
6 lessons, about 35 minutes
Minutes per lesson are an estimate, shared out by page count.
1An outage nobody could trace
3 pages
7 min
An outage nobody could trace
3 pages
2What to log and what never to log
3 pages
6 min
What to log and what never to log
3 pages
3Error handling that helps the next person
3 pages
6 min
Error handling that helps the next person
3 pages
4Monitoring and alerting basics
3 pages
6 min
Monitoring and alerting basics
3 pages
5Audit trails, retention and speaking up
3 pages
6 min
Audit trails, retention and speaking up
3 pages
6Review checklist and final assessment
2 pages
4 min
Review checklist and final assessment
2 pages
Live deck and surveys
10 slides to run live, two surveys to close the loop
Pink slides are interactive. Both surveys are anonymous; pink questions are written for this course.
Post-course feedback: 11 questions, about 2 min
- Overall rating 5 stars
- Relevant, realistic, right length, helpful activities agree/disagree grid
- What was most useful? multi-select
- Confidence before this course, and now 1-5 scale
- Confidence in log content · masking · error handling · alert tuning · audit trails grid
- In the last incident, how long did it take to find the failing request? multiple choice
- What one log message would you improve first? short text
- I can say ‘I did not log enough there’ without feeling judged. 1-5 scale
- One thing we should change or add open text
- Would you recommend this course? NPS
30-day check-in
- Have you used what you learned since the course? multiple choice
- How confident are you today? Compare with day 1 1-5 scale
- Do you know where to find the team logging standard and incident route? yes / no / not sure
- A moment where the training helped, or where you weren't sure open text
- Which topics should the next refresher focus on? ranking
Results show whether people use the training on the job, not just whether they finished it.
Make it yours
10 fields to fill in, and you're ready
Everything else is done. These are the details only your organisation knows; each one is highlighted inside the course.
- How to report an incident or near miss
{{INCIDENT_ROUTE}} - Link to the log retention policy
{{LOG_RETENTION_POLICY_LINK}} - Security team contact
{{SECURITY_CONTACT}} - Link to the engineering standards or style guide
{{ENGINEERING_STANDARDS_LINK}} - Where completion is recorded
{{LMS_OR_RECORD_SYSTEM}} - Link to the post-course and 30-day survey
{{SURVEY_2_URL}}
Show all 10 fields
- Link to the data classification policy
{{DATA_CLASSIFICATION_POLICY_LINK}} - Who to ask for help or to report a concern
{{HELP_CONTACT}} - Link to the self-paced course
{{COURSE_URL}} - Link to the baseline survey
{{SURVEY_1_URL}}
FAQ
Common questions
Can I run logging, error handling and observability standards for developers training online?
Yes. The course is self-paced and online, and the live deck lets you add a live session in the room or online.
How often is this training needed?
At onboarding, after a hard-to-trace incident, and before a logging standard is rolled out.
Who needs this training?
Developers on enterprise platforms and the code reviewers who approve their changes; run by engineering managers with L&D.
What records should I keep?
Record completion in your own LMS or record system, so you can show who finished the course and when.
Can I edit the content?
Yes, everything. Change the wording, swap scenarios for ones from your workplace, add your logo, or remove parts that don't apply.
Related templates
Often taught together
API design and microservices standards: REST, openapi and events
Back-end engineers · Engineering practice
Software testing, TDD and test automation in practice
Developers · Engineering practice
Requirements, UML modelling and software documentation
Business analysts · Engineering practice
Code review, clean code and design patterns
Junior and mid-level developers · Engineering practice
Ready to run it?
Open the live deck to see how the session runs alongside the course and both surveys.