Re-shape alerts and rebuild their duplicate links

Deduplication happens once, when an alert is written, so a change to the shape algorithm only affects alerts raised after it. This applies the current algorithm to alerts already stored: faults the old rules split apart are folded together, and alerts the new rules consider different are separated again. Alerts somebody has acknowledged, assigned or closed keep their status and link - only their fingerprint is refreshed - so nothing disappears from an operator's queue. Defaults to a dry run; the response is identical either way, so rehearse first and read shapeChanged and shapesBefore/shapesAfter before writing.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params

Ask for the alerts in a window to be re-shaped and their duplicate links rebuilt, so a change to the shape algorithm can be applied to alerts that were written under the old rules.

boolean

Rehearse only. The response is identical either way, so a dry run says exactly what would move before anything is written. Defaults to true - opt in to writing.

int32

Maximum alerts to process in this run. The response says whether the cap was hit.

date-time

Start of the window, on the published timestamp. ISO 8601.

date-time

End of the window, exclusive. ISO 8601.

Responses

Language
Credentials
Bearer
JWT
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json