Problems
Weik.io 2026.2Every problem Weik.io raises has its own page that says what raised it and how to fix it. Video
Watch: Watching the whole installation, 3:10
The video watches the whole installation from Home, Observability and Health.
This part of the video couldn't be loaded.
On this page
A problem is something that needs attention now, such as an integration whose messages fail, an agent that went offline or a certificate that expires soon. The admin UI counts problems under Needs attention on Home and lists them on Observability and on the record’s own page, and weikio problems lists the ones you may see with a command that shows more about each. Each problem links to its page here, which says what raised it, at which threshold, and the commands that fix it.
Some problems come from the hub’s metric store, and some only platform administrators see. Each page says which. Health and problems describes the Health page and how problems clear.
$ weikio problems --env productionIntegrations and deployments#
| Problem | Kind | Severity |
|---|---|---|
| An integration is failing | deployment- |
Warning or error |
| An integration restarts in a loop | deployment- |
Error |
| Memory grows day after day | deployment- |
Warning |
| An integration stopped handling messages | deployment- |
Warning |
| No agent serves the deployment | deployment- |
Error |
| A deployment runs behind its version | deployment- |
Warning |
| A single-copy deployment has no leader | deployment- |
Error |
| A single-copy deployment has two leaders | deployment- |
Error while both copies lead, then a warning |
| The leader keeps changing | deployment- |
Warning |
| A deployment matches nothing | deployment- |
Error |
APIs#
| Problem | Kind | Severity |
|---|---|---|
| An API fails on the server’s side | api- |
Warning or error |
File transfers#
| Problem | Kind | Severity |
|---|---|---|
| A transfer run failed | transfer- |
Error |
Backups#
| Problem | Kind | Severity |
|---|---|---|
| A backup is overdue | backup- |
Error |
| A backup copy failed | backup- |
Error |
Access#
| Problem | Kind | Severity |
|---|---|---|
| Two-factor sign-in is off | two- |
Warning |
Agents#
| Problem | Kind | Severity |
|---|---|---|
| An agent is offline | agent- |
Error |
| An agent never reported | agent- |
Warning |
| An agent runs an older bundle | agent- |
Warning |
| An agent’s disk is low | agent- |
Warning or error |
| An agent’s memory is low | agent- |
Warning or error |
| An agent’s revocation is pending | agent- |
Error |
The hub#
| Problem | Kind | Severity |
|---|---|---|
| An APIM instance is offline | apim- |
Error |
| A backend node is offline | backend- |
Error |
| A hub server is cut off | hub- |
Error |
| Message storage is off | message- |
Error |
| A store is filling up | store- |
Warning or error, by store |
| Retention isn’t applied | retention- |
Warning or error |
Telemetry and audit#
| Problem | Kind | Severity |
|---|---|---|
| Telemetry was lost on the way | telemetry- |
Warning |
| Telemetry is waiting on a hub server | telemetry- |
Warning or error |
| Audit records are waiting | audit- |
Warning or error |
Events#
| Problem | Kind | Severity |
|---|---|---|
| Dead letters are filling up | dead- |
Warning |
| A reader is behind | reader- |
Warning |
| A reader’s backlog is at risk | reader- |
Warning |
| A reader has dead letters | reader- |
Warning |
| A reader lost events | reader- |
Error |
| A reader has no consumer | reader- |
Error |
| A reader isn’t durable | reader- |
Warning |
| A reader isn’t receiving | reader- |
Error |
| A reader needs a restart | reader- |
Warning |
Certificates#
| Problem | Kind | Severity |
|---|---|---|
| A certificate is expiring | certificate- |
Warning or error |
| A certificate expired | certificate- |
Error |
| A certificate request is failing | certificate- |
Warning or error |