Enterprise Troubleshooting

Routing Telemetry Signals Primer

BGP/OSPF telemetry you can export safely, baseline windows, and how to pair counters with troubleshooting hypotheses.

Cover visual for Routing Telemetry Signals Primer

Overview

This primer stays routing-centric: which counters matter for adjacency health, prefix churn, and path stability. We avoid full observability platform sales language.

What is included

  • Counter cheat sheet with sane sampling windows
  • Lab: export BGP updates to a local collector
  • Hypothesis template linking signals to tests
  • Mentor review of one dashboard mock (optional)
  • Ethics note on data minimization
  • Glossary tuned for NOC handoffs
  • Short capstone: narrate a fake incident from graphs only

Outcomes

  1. Pick three signals that justify deeper packet work
  2. Avoid dashboard noise during incidents
  3. Write a one-page telemetry appendix for runbooks

Program anchor

Portrait of Marcus Yi

Marcus Yi

Campus refresh specialist; prefers diagrams over slides.

FAQ

Is programming required?

Light YAML/JSON edits only; we do not teach full-stack development.

Which collectors are used?

Open-source examples only; no vendor-specific licensing included.

Will this teach cloud cost ops?

No. We mention billing dashboards only as out-of-scope references.

Participant notes

“Routing Telemetry Signals Primer is short but dense. I wanted one more week of async Q&A; still worth it for the hypothesis template.”
Yuki · 4/5 · survey