Last Modified: Jul 15, 2026
Affected Product(s):
F5OS F5OS-C
Known Affected Versions:
F5OS-C 1.8.1, F5OS-C 1.8.2
Fixed In:
F5OS v2.0.0
Opened: Nov 21, 2024 Severity: 2-Critical
Telemetry data export intermittently fails, when handling large volumes of data. Memory errors may get logged.
At the exporter end, some data will be missing, causing gaps in the graphs for certain periods.
When telemetry is configured with "all" or "metrics"
Configure only the required instruments individually instead of using the "metrics" or "all" options. Don't configure the "tmstat" instrument which will flood data and drop most of it.
When telemetry is configured with "all" or "metrics", it is a culmination of a lot of other instruments like optics, platform, container etc. Data getting dropped due to the large volumes pushed since the queue pushing to OTEL has a limitation on size. Sometimes memory issues from platform-monitor or otel collector arise if limit is not set for the queue pushing otel data. To fix this, "container" instrument which contributes to a large share of data in both "metrics" and "all" instruments has been removed. For observability, a new stat queueDropOnMaxSizeMetricCount is introduced to monitor queue data drops and with this fix, no data drops seen! Although an exception, "tmstat" is not a part of "all" or "metrics" and this is an instrument used for deeper diagnostics. When "tmstat" is configured, data loss is inevitable since it pushes huge amount of data alone.