As we automate more and more, having visibility into how your F5 infrastructure is running is even more important. F5 BIG-IP Telemetry Streaming can help gather and send all the telemtry data one could want to know, including syslog, device stats, and application stats, which is better than the typical syslog/snmp configuration.
Setting up Telemetry Streaming can be really simple and rather complicated at the same time. Over the years I've had a need to test and tweak telemetry for different scenarios.
This article aims to provide a quick and simple walk through of how to setup F5 Telemetry Streaming with one of the more popular logging and analytics systems available, Splunk. Splunk Cloud Trials are great for quick and simple solution development in this manner.
Update the fqdn from the 'Splunk Cloud Platform URL' in our email, and the Splunk Authorization token from setting up the HTTP Event Collector. Port 8088 is default for the event collector running next to the main managemnt site on 443.
After a couple of minutes you should start to see the telemetry flowing. Be sure to search the right index (index=*) and scope the time for the last 15 minutes
EXPLORE ALL THE DATA!
To recap, this article provides a quick walk through of configuring Splunk Cloud and BIG-IP Telemetry Streaming. BIG-IP Telemetry Streaming is a comprehensive solution for capturing and shipping BIG-IP telemetry (syslog, device stats, and application stats) for deeper analysis.