If you are familiar with the BIG-IP system, and generally familiar with REST and
using APIs, this section contains the minimum amount of information to get you
up and running with Telemetry Streaming.
Components of the declaration
This section provides more information about the options in the Quick Start example, and breaks down the example declaration into each class so you can understand the options when composing your declaration. The tables below the examples contain descriptions and options for the parameters included in this example only.
For a list of all the Telemetry Streaming classes and options, see Using Telemetry Streaming.
If there is a default value, it is shown in bold in the Options column.
The first few lines of your declaration are a part of the base components and define top-level options. When you POST a declaration, depending on the complexity of your declaration and the modules you are provisioning, it may take some time before the system returns a success message. Note that the controls class is optional and used for logging and debugging (see Logging).
||Describes top-level Telemetry Streaming options. The optional class for controls must always be Controls, do not change this value. Controls are for logging and debugging.
||info, debug, error
||This value determines how much information you want Telemetry Streaming to log. See the Logging section for more information.
Telemetry System class
The next lines of the declaration define the target system. You can define and configure the system poller inside of the System declaration to collect and normalize statistics. These statistics include device statistics, virtual server statistics, pool statistics, individual pool member statistics, and more. For more information, including an optional iHealth poller, see Telemetry System class.
||The class for Telemetry System must always be Telemetry_System, do not change this value.
||This value Polls a system on a defined interval for information such as device statistics, virtual server statistics, pool statistics and much more.
Telemetry Listener class
The next lines of the declaration sets the Event Listener, on both TCP and UDP protocols, that can accept events in a specific format and process them. Currently, the TS Listener sends all logging telemetry data.
To see the type of information that the event listener processes, see Example Output.
||The class for listener must always be Telemetry_Listener, do not change this value.
||Specifies the port of the TCP and UDP listener
Telemetry Consumer class
The next lines of the declaration sets the Consumer, which accepts all telemetry information from whatever systems you configure it to. The consumer provides the tools to process that information. To see examples of configurations for consumers like Splunk, Azure Log Analytics, AWS CloudWatch, AWS S3, Graphite, and others, see the Consumer class section of this guide.
||The class for consumer must always be Telemetry_Consumer, do not change this value.
||Splunk, AWS_S3, etc.
||Specifies the consumer type you would like to send Telemetry information to. See the Consumer class section for more information.
||The address of the instance that runs the HTTP event collector
||The protocol of the consumer
||The port of the consumer system
||The secret password to use when sending data to the consumer system