Update an existing alert configuration.
Immutable fields — the following fields cannot be changed after creation.
If the request body contains a different value, the API returns 400:
alert_type_id
Editable fields — all other fields can be updated, including name.
If the new name conflicts with an existing alert owned by the same user,
the API returns 409.
For Phase 2 (dynamic/non-preset) alert types, changes are synced to
SignOz before the database is updated. If SignOz rejects the change,
the database remains untouched.
Bad request. Possible reasons:
- Invalid alert ID (not a valid UUID)
- AJV schema validation failure (missing required fields, extra properties)
- Attempted to change an immutable field (
alert_type_id) - Invalid threshold_config values (e.g. expected_bitrate <= 0, deviation_percentage out of range)
Unauthorized — missing or invalid JWT.
Forbidden — user lacks write access to the specified contracts/groups.
Not found. Possible reasons:
- Alert configuration does not exist or belongs to a different account
- Alert type does not exist
Duplicate alert name — another alert with the same name already exists for this user.
Internal server error (including SignOz sync failures).