F5 Telemetry Streaming

Welcome to the F5 Telemetry Streaming User Guide. To provide feedback on this documentation, you can file a GitHub Issue, or email us at solutionsfeedback@f5.com.

Important

This the documentation for the latest version of Telemetry Streaming, if you want to see the documentation for a long term support (LTS) version, use the version selector on the top left (for details, see Support information on GitHub).

Introduction

Telemetry Streaming (TS) enables you to declaratively aggregate, normalize, and forward statistics and events from the BIG-IP to a consumer application. Telemetry Streaming is an iControl LX Extension delivered as a TMOS-independent RPM file, and uses a declarative model, meaning you provide a JSON declaration rather than a set of imperative commands. To use Telemetry Streaming, you POST a single JSON declaration to Telemetry Streaming’s declarative REST API endpoint.

See our Telemetry Streaming overview video:

This guide contains information on downloading, installing, and using the Telemetry Streaming Extension. Use the navigation panes, and/or the Next and Previous buttons to explore the documentation.

You can click the following links to go directly to a specific Push Consumers or Pull Consumers:

Push Consumers	Supports System Poller	Supports Event Listener
Splunk	yes	yes
Microsoft Azure Log Analytics	yes	yes
Microsoft Azure Application Insights	yes (metrics only)	no
AWS CloudWatch	yes (metrics only)	no
AWS S3	yes	yes
Graphite	yes	yes
Kafka	yes	yes
ElasticSearch	yes	yes
Sumo Logic	yes	yes
StatsD	yes (metrics only)	no
Generic HTTP	yes	yes
F5 Beacon	yes	yes
Fluentd	yes	yes
Google Cloud Operations Suite’s Cloud Monitoring	yes (metrics only)	no
Google Cloud Logging	yes	yes
DataDog	yes	yes
OpenTelemetry Exporter	yes (metrics only)	partial (converts logs to metrics)

Pull Consumers	Supports System Poller	Supports Event Listener
Default Pull Consumer	yes	no
Prometheus Pull Consumer	yes (metrics only)	no