Skip to main content
🔒 Preview mode. The first 15 Foundations lessons are free; this one is Pro. Start a 7-day trial to unlock the editor, AI hints and the rest of the curriculum. Card required, cancel any time in Dashboard.
Start 7-day trial →
⚡
← Courses
›
DevOps for Python services
›
Module 5 · Cloud, IaC, Secrets, Cost · Recap
›
Tracing: Jaeger / Tempo
quiz
89 / 104
🇺🇸
EN
▼
↗
Share
⋯
More
+100 XP
📋
Task
📖
Theory
🤖
AI Help
Task
📝 **Question:** First place to look when latency spikes across microservices? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
🎯 Quiz
Question
📝 **Question:** First place to look when latency spikes across microservices? 📋 Pick the right answer. 💡 **Hint:** Re-read the theory above if unsure.
A
Logs — pipe every gateway and downstream service log through `kubectl logs` and grep for request IDs with long durations.
B
Trace one slow request — see which service is the bottleneck. Avoids the 'which log to grep' game.
C
Restart every pod in a rolling sweep — half of cross-service latency spikes resolve themselves after the connection pools rebuild.
D
Scale the nodes vertically — moving to a larger instance type fixes most p99 latency anomalies before deeper root-cause work.
Submit answer
💬 Discussion
Be the first to ask a question or share a tip.
Sign in
to join the discussion. Reading is free.
Loading discussion…