HEART performance.overloaded H-05002
Overloaded. More work is arriving than can be handled.
| Code | HEART performance.overloaded; inside a message "code": "performance.overloaded" |
|---|---|
| H-number | H-05002: area 05, code 002 |
| Area | performance: Speed, load, heat |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Servers, apps and gateways |
Likely causes
- A peak in demand: a sale on a web shop, many devices reporting at once.
- Fewer workers or servers than normal, after some failed.
- A client or device sending far too many requests.
- Heavy background work at a busy time.
How to fix or prevent it
- Check whether the load is real demand or a fault (one client sending too much).
- Add capacity, or turn on more workers.
- Limit the rate of busy clients, and delay background work.
What the HEART does by itself
It raises a warning, and may throttle low-priority work if a Playbook allows it. It does not add paid capacity by itself: it asks a person. It resolves when load is back within capacity.
When to call service
If the load comes from a fault or an attack, or capacity cannot be added.
Related codes
performance.backlogH-05003: Backlog growingperformance.slowH-05001: Responses slowsecurity.anomalyH-11007: Security anomaly
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)