Telemetry Streaming (TS) explainer
Paste the JSON you POST to /mgmt/shared/telemetry/declare and it reads it back: it confirms the top-level Telemetry class, reads the optional Controls, and walks every class-object grouped by its role in the telemetry pipeline: the data sources that produce telemetry (system pollers, event listeners), the consumers that forward it out (Splunk, Azure, AWS, DataDog, Prometheus, and the rest of the catalogue), and the grouping and endpoint classes. It flags the pipeline gaps that make a declaration succeed but do nothing. TS is the third F5 Automation Toolchain extension: AS3 and DO configure the box, TS observes it.
Networking🔒 Decoding runs locally in your browser. Nothing you paste leaves this page.
Paste a TS declaration to see it explained.
API endpointGEThttps://ronutz.com/api/v1/telemetry-streaming-explainerDocumented, not served. Opens the specification.
References
- F5 BIG-IP Telemetry Streaming: Quick Start (the base Telemetry declaration, the Controls class with logLevel default info, the Telemetry_System / Telemetry_Listener / Telemetry_Consumer classes, default Listener port 6514, Consumer protocol default http, and the /mgmt/shared/telemetry/declare and /info endpoints)
- F5 BIG-IP Telemetry Streaming: Using TS (the full class index and the complete push and pull consumer type catalogue: Splunk, Azure, AWS, Graphite, Kafka, ElasticSearch, DataDog, Generic HTTP, OpenTelemetry, Prometheus, and more)
- F5 BIG-IP Telemetry Streaming: Telemetry System class (the system poller and the iHealth poller, and the rule that an iHealth poller must be attached to a Telemetry_System)
- F5 BIG-IP Telemetry Streaming: Example Declarations (the base declaration, the referenced Telemetry_System_Poller pulling from an additional BIG-IP, and the Telemetry_Namespace examples)
- F5 BIG-IP Telemetry Streaming: Troubleshooting (a Telemetry_System used for metrics must define systemPoller; event ingest needs a Telemetry_Listener whose port matches the BIG-IP log configuration)