v1.19.0

Updated the documentation for Telemetry Streaming v1.19.0. This release contains the following changes. See the Document revision history for more information and links.

• Added a new troubleshooting entry providing memory threshold information
• Added new Event Listener endpoints for sending debug messages to an Event Listener
• Updated the Splunk Consumer documentation with the new compressionType property, and added a related troubleshooting entry
• totNativeConns and totCompatConns are now exposed on SSL profile stats
• Added the swap metric to the system group
• Trace full payload now sent to StatsD Consumer
• System Poller recurring scheduling changed so that System Poller executions do not overlap
• Added a note to iHealth Poller stating it must be attached to a System
• Added a bullet item to About Pull Consumer stating if a poller was attached to two systems, the response contains data from both
• Added a note to the Important list for Namespaces about naming objects

Issues Resolved:

• Fixed Route Domain ID handling for Virtual Server and Pool stats
• Splunk debug output does not log HTTP Response payload, GitHub #109
• Update example output for maxConns, pktsIn, pktsOut, and totConns
• Tracer unable to access destination directory
• Tracer(s) from other namespaces should not stop when namespace-only declaration posted
• Removed excessive data formatting from tracer

v1.18.0

Updated the documentation for Telemetry Streaming v1.18.0. This release contains the following changes. See the Document revision history for more information and links.

• Added new endpoints for individual namespaces
• Added support for TLS client authentication for the Generic HTTP consumer
• Added response logging to Event Listener page
• Added a note to AWS CloudWatch and AWS S3 about root certificates for AWS services being embedded within Telemetry Streaming

Issues Resolved:

• Fix Event Listener startup errors that might cause restnoded to crash
• Splunk multiEvent format should ignore ‘References’

v1.17.0

Updated the documentation for Telemetry Streaming v1.17.0. This release contains the following changes. See the Document revision history for more information and links.

• Added support for configuring proxy settings on Generic HTTP consumers, GitHub #92
• Added support for configuring proxy settings on Splunk consumers, GitHub #85
• Added a timestamp for APM Request Log output, GitHub #91
• Added support for TLS client authentication to the Kafka consumer, GitHub #90
• Added an F5 Internal Only push consumer for F5 Cloud
• Added the ability to use the Splunk multi-metric format, currently EXPERIMENTAL
• Tracefile now stores up to 10 items
• Deprecated TS support for the Splunk Legacy Format
• Posting a declaration while a previous declaration is still processing now returns an HTTP 503 status code

Issues Resolved:

• Fixed error where unavailable Custom Endpoint would return HTTP 500

v1.16.0

Updated the documentation for Telemetry Streaming v1.16.0. This release contains the following changes. See the Document revision history for more information and links.

• Added support for the Telemetry_Namespace class in declarations posted to the /declare endpoint
• Added new Namespace PullConsumer endpoint
• Added support for Custom Endpoints. Moved the Custom Endpoint page from an Appendix to Using Telemetry Streaming
• TS now includes _ResourceId if available for Azure Log Analytics consumer, and metadata calls are now only happening upon consumer(s) load

Issues Resolved:

• Fixed issue when TS incorrectly processing iRule stats with multiple events

v1.15.0

Updated the documentation for Telemetry Streaming v1.15.0. This release contains the following changes. See the Document revision history for more information and links.

• Updated the default hostname for the StatsD consumer

Issues Resolved:

• Fixed syslog event hostname parsing for VCMP hosts
• Resolve memory leak in ElasticSearch consumer, by replacing ‘elasticsearch’ library with ‘request’ library

v1.14.0

Updated the documentation for Telemetry Streaming v1.14.0. This release contains the following changes. See the Document revision history for more information and links.

• Added support for AWS CloudWatch Metrics
• Added an EXPERIMENTAL feature to specify fallback hosts for generic HTTP consumers
• Added F5 Beacon as a Generic HTTP consumer
• Added cipherUses stats for Client and Server SSL profiles
• Added a troubleshooting entry for a restjavad issue
• Added a note to the Exporting data from AVR page about AVR caveats with TS and BIG-IQ
• Updated the introduction for the experimental Appendix B: Configuring Custom Endpoints
• Added support for BIG-IP 16.0

Issues Resolved:

• Fixed Event Listener parsing when receiving multiple events

v1.13.0

Updated the documentation for Telemetry Streaming v1.13.0. This release contains the following changes. See the Document revision history for more information and links.

• Added statusReason and monitorStatus fields to System Poller output for BIG-IQ Analytics
• Added comprehensive troubleshooting entry for why data may not be showing up in a consumer
• Updated the Event Listener page

Issues Resolved:

• Fixed inconsistency in GSLB output: return empty object instead of ‘undefined’
• Fixed Azure consumer memory leak when calling metadata service on an instance where it is unavailable
• Updated Azure Log Analytics dashboard example (GitHub #39)
• Fixed lodash Prototype Pollution vulnerability
• Fixed Splunk legacy format missing poolMemberStat data

v1.12.0

Updated the repository for Telemetry Streaming v1.12.0. This release contains the following changes. See the Document revision history for more information and links.

• Added a new consumer for Prometheus (see Prometheus Pull Consumer)
• Updated the Pull Consumer page and added an example for using push and pull consumers in the same declaration (see Pull Consumers)
• Added support for IAM Roles with AWS_S3 Consumer (see AWS S3)
• Added TCP support to the StatsD consumer (see StatsD)
• Added a note to Splunk Legacy format stating if the legacy format is used, it ignores events from the Event Listener

Issues Resolved:

• Added a timeout to Azure metadata service HTTP requests to fix an issue where the Azure Consumer was slow when running in a non-Azure environment
• Fixed renameKeys for networkInterfaces with multiple digits (GitHub #18)

v1.11.0

Updated the repository for Telemetry Streaming v1.11.0. This release contains the following changes. See the Document revision history for more information and links.

• Added a new consumer for Azure Application Insights
• Added support for Azure Managed Identities for Azure Log Analytics and Azure Application Insights
• Added support for AzureGov for Azure consumers using an optional region property
• Added a new page for the Pull consumer and renamed existing Consumer page to Push consumer
• Added a new page detailing how to delete the configuration produced by TS
• Renamed Google StackDriver to Google Cloud Monitoring

Issues Resolved:

• Fixed Regular Expression Denial of Service vulnerability and improved start up time on node v4.x and v6.x
• Fixed error when Splunk consumer (configured with ‘legacy’ format) tries to forward event from Event Listener (GitHub #30)
• Fixed crash in Kafka consumer on attempt to close idle connections to brokers (GitHub #17)

v1.10.0

Updated the repository for Telemetry Streaming v1.10.0. This release contains the following changes. See the Document revision history for more information and links.

• Added a feature (currently EXPERIMENTAL) for configuring custom endpoints
• Added ifAnyMatch functionality to the existing value-based matching logic
• Added support for F5 devices with multiple hosts (see the FAQ)

Issues Resolved:

• Event Listener unable to classify AFM DoS event
• Splunk legacy tmstats - include last_cycle_count
• Splunk legacy tmstats - add tenant and application data
• Declarations with large secrets may timeout
• Passphrases should be obfuscated in consumer trace files
• Add ‘profiles’ data (profiles attached to Virtual Server) to ‘virtualServers’
• Use baseMac instead of hostname to fetch CM device (GitHub Issue 26)
• cipherText validation when protected by SecureVault
• Caching data about the host device to speed up declaration processing