HEART performance.slow H-05001
Responses slow. Responses take much longer than normal.
| Code | HEART performance.slow; inside a message "code": "performance.slow" |
|---|---|
| H-number | H-05001: area 05, code 001 |
| Area | performance: Speed, load, heat |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Servers, apps, gateways, any product that answers requests |
Likely causes
- A slow database or outside service.
- Too little CPU or memory for the load.
- A full disk or a failing one.
- A slow or unstable network link.
How to fix or prevent it
- Look at what is slow: the alert gives the time taken against the normal time.
- Check the services it waits on, and their own speed.
- Check CPU, memory and disk use.
- Add capacity, or move heavy work to a quieter time.
What the HEART does by itself
It raises a warning when responses pass the product's stated limit, such as 1.5 s at the 95th percentile, and resolves it when they are back under it. A Playbook may clear a cache or throttle low-priority work, within its guards.
When to call service
If it lasts and you cannot find a cause in load, network or outside services.
Related codes
performance.overloadedH-05002: Overloadedperformance.backlogH-05003: Backlog growingconnectivity.link-unstableH-03002: Network link unstable
Inside a message a code is written bare, "code": "storage.full". In logs, tickets, documents and searches it is written
HEART storage.full. Things that simply happen, such as system.started, are event types, not faults.
The codes are defined in Part 3, Section 5.4, and their H-numbers in Section 5.7.
All of it, as data: fault-codes.json.
All fault codes, by area · All fault codes, by H-number · Problem types (API errors)