Raises an alert for something nothing automatic would have caught - a report from a customer, a figure that looks wrong. It is published through the platform's own alert pipeline rather than written straight to the queue, so everything that processes alerts handles it exactly as it handles one the platform raised: it is deduplicated against recent alerts of the same shape, given an owner from the ownership rota, and forwarded wherever alerts are forwarded. Who raised it is stamped on the alert's creation history entry and repeated in the message, which is what reaches the destinations that never see the history. Publishing is asynchronous, so nothing is returned and the alert appears in the queue a moment later; search for it rather than expecting an id back. Severities the platform does not store are not stored here either - LOW is forwarded but never queued.
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
No Content - the alert has been published