list_event_rules

GET

/api/v1/event-rules

curl --request GET \
  --url https://example.com/api/v1/event-rules \
  --header 'Authorization: Bearer <token>'

Authorizations

• bearer

Responses

200

Every stored event rule

Media typeapplication/json

Array<object>

A stored event rule (API shape; the engine compiles enabled ones).

object

clear_pattern

string | null

created_at

required

string format: date-time

enabled

required

boolean

id

required

string format: uuid

match_kind

required

How a rule’s pattern is matched against the event text.

string

Allowed values: substring regex unknown

min_count

required

integer format: int32

name

required

string

node_id

string | null format: uuid

pattern

required

string

severity

required

How serious an alert is. Variants are declared low → high so the derived Ord ranks Critical above Warning above Info.

string

Allowed values: info warning critical

source_id

string | null format: uuid

source_kind

string | null

ttl_secs

required

integer format: int32

window_secs

required

integer format: int32

Example

[
  {
    "match_kind": "substring",
    "severity": "info"
  }
]

401

No valid bearer token

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}

403

Role below Admin

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}

503

This core has no write side (skeleton mode)

Media typeapplication/json

The ADR-019 envelope every failure renders as. pub(crate) and schema-bearing so the OpenAPI document can name one error shape for every endpoint (ADR-035) instead of leaving 4xx/5xx bodies undescribed — a client that has to guess the failure shape ends up parsing the success shape and reading undefined.

object

error

required

object

code

required

Stable machine-readable code. Clients branch on this, never on the message.

string

message

required

Operator-facing sentence. Safe to display; never carries an internal error’s own text.

string

Example^generated

{
  "error": {
    "code": "example",
    "message": "example"
  }
}