Restoring capacity is only the start of recovery. Follow a small queue calculation to see how new arrivals compete with old work, and how to test the prediction safely.
At 14:15, one region has delayed reports. Eight minutes later, you know about another. Keep people informed without promising a fix you cannot yet see.
A deployment looked suspicious until older-version jobs told a different story. Explain decisions using the clues and authority available when people made them.
It might be a backup job. It might need urgent attention. Bring the observation to a specialist without losing the service investigation or spreading sensitive records.
Twenty failed exports can be 0.2% of the fleet and 20% of one region. Follow the counts to see what each metric can tell you and what remains outside its view.
Send a local service’s telemetry to the wrong port, then compare its recorded job state with missing spans. Repairing telemetry delivery does not bring every old trace back.
The slow trace is useful. The command, restart and comparison that explain it are useful too. Keep them together as you follow a local export from acceptance to completion.