HEART software.error-spike H-06001
Error spike. Errors are happening far more often than normal.
| Code | HEART software.error-spike; inside a message "code": "software.error-spike" |
|---|---|
| H-number | H-06001: area 06, code 001 |
| Area | software: Crashes, versions, updates, settings |
| Typical severity | warning. A product may set another for its own case. |
| Applies to | Servers, apps and any product with logs of errors |
Likely causes
- A new release with a bug.
- An outside service returning errors.
- Bad input from one client or device.
- A setting changed by mistake.
How to fix or prevent it
- Look at which errors grew, and since when.
- Compare with recent releases or setting changes, and roll back if one matches.
- Check outside services it uses.
What the HEART does by itself
It raises a warning when the error rate is far above normal. A Playbook may roll back a recent change or switch providers, within its guards. It resolves when the rate is back to normal.
When to call service
If the errors affect customers or the main job, and no recent change explains them.
Related codes
software.crashedH-06002: Crashedconnectivity.dependency-unreachableH-03003: A service it relies on cannot be reachedsoftware.config-invalidH-06005: Settings invalid
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)