Oaktown Tech / practical labs
One failed link. How many useful alerts?
Change a small network’s observed states. Group related symptoms without making the independent alarms or uncertainty disappear.
Read the text guide: instructions and limitations without interactive controls.
Experiment workbench
Return to the challenges ↑This is a synthetic monitoring snapshot, not a network scan. Change an observation and see what can be grouped and what must stay visible.
Set the scene
Three unreachable observations share a path. Predict how many groups you will get.
See the result ↓Fewer groups. The same evidence.
↑ Change the observationsWhy did it group that way?
The dependency model
A child’s reachability event joins an upstream group only when all of its configured parents are observed Unreachable. An Up or Unknown parent blocks that inference.
- Edge router
- Backhaul
- Site switch (also has Backup path as a parent)
- Camera
- Site switch (also has Backup path as a parent)
- Office switch
- Backup path (second parent of Site switch)
- Backhaul
These are monitoring dependencies, not a wiring diagram. An Up backup observation does not prove that the backup can carry the application.
Keep the evidence
Nothing is deleted or silently marked healthy. Each edit creates a new snapshot; this lab does not reconstruct a timeline.
Current observations and original events
| Node | Observed state | Configured parents |
|---|
| Event | Node | Kind | Evidence |
|---|
Try to break the tidy story
- Start with the failed backhaul, then add both independent alarms. Did either vanish?
- Bring the backhaul Up. Leave the switch and camera Unreachable. Where does the remaining group begin?
- Add an Up backup path. Then change it to Unknown, then Unreachable. Which state permits the site switch to join its upstream parents?
This finite model has no polling, timing, event history, maintenance windows, flapping logic or production alert suppression. All examples are invented. Its job is to sharpen the questions you ask of a real monitoring system.
Context: Alertmanager grouping and inhibition concepts. This exercise is not a certification of equipment, construction, security, or service performance.