Alert routing rules

Reorder the routing rules of an integration

Rewrites the evaluation order: the first UUID in order becomes position 0 and is tried first. This changes which rule wins for an alert that several rules match, so it changes routing, not just presentation. UUIDs that do not belong to this integration are ignored; rules omitted from the list keep their previous position, which can leave two rules sharing one — send the complete list. Returns the rules in their new order.

post/api/v1/observability/integrations/{integration}/routing-rules/reorder

Request

Base URL: https://wardenpoint.com (the document declares no server; this is the origin it was published from)
URL: https://wardenpoint.com/api/v1/observability/integrations/{integration}/routing-rules/reorder
Auth: API key in header X-API-Key

Path parameters

integrationstring uuid required

Integration UUID.

Request body

orderstring[] required

Every routing-rule UUID of this integration, most important first.

Response

Rules in their new order.

Example response

{
  "data": [
    {
      "label_matchers": [
        {
          "key": "service",
          "value": "checkout"
        }
      ]
    }
  ]
}

Changes

No recorded changes to this operation across all 1 revision of this API.