Bug ID 1982773: OTel telemetry data for a system controller or blade stopped after its reboot

Last Modified: Jul 15, 2026

Affected Product(s):
F5OS F5OS-C(all modules)

Fixed In:
F5OS v2.0.0

Opened: Jul 13, 2025

Severity: 2-Critical

Symptoms

If a system controller is rebooted or a blade is rebooted or removed and inserted back, OTel telemetry data is stopped for it.

Impact

OTel telemetry data is stopped after a blade or system controller reboot.

Conditions

System controller or blade reboot, blade removed and inserted back.

Workaround

Blade reboot scenario - making changes in the exporter path like disabling and enabling back, change in instrument list might help. Restartinig diag-agent on the active system controller might help. In a system controller reboot scenario - restart diag-agent on the active system controller.

Fix Information

Fixed an issue causing OTel telemetry data to stop being collected after a reboot.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips