Telemetry was lost on the way
Weik.io 2026.2The hub lost logs, metrics or traces in the last 15 minutes, and the detail gives each cause with the action that fixes it.
| Kind | Severity | Who sees it |
|---|---|---|
telemetry- |
Warning | Platform administrators, in a list that isn’t narrowed to an environment or a project |
What it means#
The hub lost some of the logs, metrics or traces it was sent in the last 15 minutes, so the charts and searches of that time miss part of what happened.
What raises it#
The hub counts the batches its ingest neither stored nor kept on disk for later, and the metrics the metric store refused over its limit on new series, over the last 15 minutes. The detail gives what was lost, the senders of batches too large for one request, and an action for each cause. The problem needs the hub’s metric store, which every installation has unless it was set up without one.
What to check#
See the stores and what the hub received:
$ weikio platform healthOn a hub server, in the stack’s folder, check the stores:
$ docker compose run --rm infra weikio-backend doctorHow to fix it#
Follow the action the detail gives. A store that didn’t answer is started again with docker compose up -d in the stack’s folder, a sender whose batches are too large is named so you can find it, and metrics refused over the limit on new series usually come from an integration’s own counter with a tag that changes with every message, such as an order id.