Releases: F5Networks/f5-telemetry-streaming
v1.9.0
Updated the repository for Telemetry Streaming v1.9.0. This release contains the following changes. See the Document revision history for more information and links.
- Added support for gathering configuration information and statistics for GSLB Wide IP and Pools
- Username and passphrase are now optional on the AWS CloudWatch consumer
- Added detailed information about character encoding and Telemetry Streaming
- Added a FAQ entry to define the F5 Automation Toolchain API contract
Issues Resolved:
- Basic auth does not work with ElasticSearch consumer
- Some Splunk legacy tmstats datamodels have a period in property name instead of underscore
v1.8.0
Updated the repository for Telemetry Streaming v1.8.0. This release contains the following changes. See the Document revision history for more information and links.
- Added support for Google StackDriver as a consumer
- Added a new page for Data Modification, which includes support for Action Chains, and includeData and excludeData filtering
- Added machineId to System Poller output
- Added reference to pools in virtual server data
Issues Resolved:
- Improved error handling to preserve stack traces
v1.7.0
Updated the repository for Telemetry Streaming v1.7.0. This release contains the following changes. See the Document revision history for more information and links.
- Added a new Consumer for Fluentd
- Added a note to Splunk Legacy format stating TS 1.7.0 and later gathers additional data from tmstats tables to improve compatibility with Splunk Legacy consumers
- Added a troubleshooting entry and other notes about the /dist directory going away on GitHub, and the TS RPM being available as a release Asset
- Added an FAQ entry about TS collecting non-identifiable usage data
- Updated the maximum number of concurrent established TCP sockets per consumer to 5
Issues Resolved:
- Splunk Tmstat table data is being overwritten when forwarded to Splunk
- Broken promise chain when loading config file.
v1.6.0
Updated the repository for Telemetry Streaming v1.6.0. This release contains the following changes. See the Document revision history for more information and links.
- Support for Data Tagging API
- Hardening
v1.5.0
Updated the repository for Telemetry Streaming v1.5.0. This release contains the following changes. See the Document revision history for more information and links.
- Added support for Carrier Grade NAT (CGNAT) event logs.
- Telemetry Streaming now collects mask and ipProtocol for virtual servers.
- Telemetry Streaming now collects the system status information: devicegroup, asm_state, last_asm_change, apm_state, afm_state, last_afm_deploy, ltm_config_time, and gtm_config_time.
- Added iRules support to system poller stats.
- Added a Troubleshooting entry about a self-signed certificate error. Also added a related allowSelfSignedCert row to the Advanced Options table.
Issues Resolved:
- Elastic Search Unable to parse and index some messages with previously used keys
- Elastic Search event data objects containing consecutive periods will be replaced with a single period
- Splunk Host property is null for TS events
v1.4.0
Updated the repository for Telemetry Streaming v1.4.0. This release contains the following changes. See the Document revision history for more information and links.
- Added a new troubleshooting entry for an error that can occur with the ElasticSearch consumer
- Added the schema files from previous releases to the GitHub repository
- Updated Validating a declaration to clarify the schema URL to use
- Updated the documentation theme and indexes.
Issues Resolved:
- System Poller throws unhandled exception “socket hang up” on attempt to fetch stats.
v1.3.0
v1.2.0
v1.1.0
Telemetry Streaming v1.1.0 contains the following changes:
- Added StatsD as a consumer
- Added generic http as a consumer
- The Event Listener now supports UDP in addition to TCP, allowing local device logs to be forwarded
- Standardized date/time fields to ISO string
- Updated the Azure Log Analytics example dashboard, and included a link to it in the documentation
- Added validation example using VS code to documentation
Issues Resolved:
- Corrected an issue that caused Kafka consumer to force TLS. Users can now configure with protocol property values
binaryTcpTls
orbinaryTcp
- Corrected an issue that prevented Azure Log Analytics from processing TS events
- Corrected an issue that caused disk latency system statistics to be employ on BIG-IP 14.1
See the Document Revision History for more information and links.