![]() ![]() The facility parameter is for identification of location/facility in which the BIG-IP is located (such as ‘Main Data Center’, ‘AWS’, or ‘NYC’). In Telemetry Streaming v1.6.0 and later, you must use the facility parameter with the legacy format to specify a Splunk facility in your declarations. Telemetry Streaming 1.7.0 and later gathers additional data from tmstats tables to improve compatibility with Splunk Legacy consumers. This includes GET requests to the SystemPoller API because the data is not pulled unless it is a legacy Splunk consumer. To poll for any data involving tmstats you must have a Splunk consumer with the legacy format as described in this section. To see more information about using the HEC, see Splunk HTTP Event Collector documentation. To see more information, see F5 Analytics iApp Template documentation. ![]() The format property can be set to legacy for Splunk users who wish to convert the stats output similar to the F5 Analytics App for Splunk. We recommend using the Splunk default format, or Splunk multi-metric format. This means there will be no further TS development for the Splunk Legacy format. The Splunk Legacy format has been deprecated as of Telemetry Streaming 1.17, and has entered maintenance mode. Additions to the OpenTelemetry Exporter consumer.Using IAM roles for Google Cloud Logging.Using IAM roles for Google Cloud Monitoring.Additions to the Cloud Monitoring consumer.Google Cloud Operations Suite’s Cloud Monitoring.Additions to the AWS CloudWatch consumer.Using Microsoft Managed Identities for Application Insights.Additions to the Application Insights consumer.Using Microsoft Managed Identities for Log Analytics. ![]() Additions to the Azure Log Analytics consumer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |