-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
AT:
- If a telemetry request fails
- retry the request a configurable number of times
- log the exception message on WARN
- log the full exception stacktrace on DEBUG
- When telemetry is activated (after engine start or when telemetry is activated via API)
- immediately schedule the telemetry task for a first ping; then switch to periodic reporting
- If scheduling the telemetry task fails, throw an exception (so that the ToggleTemetryCommand fails; but do not interrupt process engine bootstrap)
- Make reporting period configurable
- The command counters should only be reset when the telemetry was sent successfully