How cisco-ie/telemetry works
This repository is a collection of network telemetry datasets for anomaly-detection research, not an application or processing pipeline. The principal workflow is for a researcher to choose a traffic or anomaly scenario and use its data alongside header definitions and event context; topology documentation supplies network context. The README documents the CSV/header/case-file relationship, but no source excerpts describe processing or runtime behavior. Dataset 11 and the detailed scenario captures under 12 are represented from the tree; their internal relationships are not inferred.
Main entry points: 0 Zero-load baseline · 1 500 Gbps baseline · 2 BGP clear sets · 4 Flap and admin sets
Components 12
Scenario datasets
- Zero-load baseline
0 - 500 Gbps baseline
1 - BGP clear sets
2 - Flap and admin sets
4 - Transceiver pull
10 - CSV measurements
0/baseline_no_anomaly.csv.gz - Header definitions
0/baseline_header.txt
Telemetry captures
- Router telemetry
11/Dataset - Network scenarios
12 - Event records
11/Dataset/events.csv.gz
Network context
- Topology documents
topology_description_docs
Other components
- Researcher
Connections 10
- Researcher → Zero-load baseline: selects
README.md - Researcher → 500 Gbps baseline: selects
README.md - Researcher → BGP clear sets: selects
README.md - Researcher → Flap and admin sets: selects
README.md - Researcher → Transceiver pull: selects
README.md - Zero-load baseline → CSV measurements: includes CSV
README.md - Zero-load baseline → Header definitions: includes definitions
README.md - Researcher → Router telemetry: uses
- Researcher → Network scenarios: uses
- Researcher → Topology documents: consults
README.md