Cross-layer investigations
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
follow a symptom through JVM, database, network, and Kubernetes layers.
Planned topics
- Walk layers deliberately: application, JVM (GC, threads), OS and container limits, network, database, dependencies.
- Use correlating signals: same timestamps across layers; compare healthy and unhealthy instances.
- Typical cross-layer causes: GC pauses from a too-small memory limit, CPU throttling, DNS delays, packet loss, noisy neighbors, query plan change.
- Keep a layer map and note which evidence ruled out each layer.
Draft outline details
Demonstration
Table: layer | tool | signal | verdict. Example rows: JVM | GC logs | pause length; container | cgroup throttling metrics | throttled periods; network | latency percentiles per hop.
Check your understanding
How do you use a healthy instance in an investigation?
Show answer
Compare it with the unhealthy one to isolate the difference.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.