Fix asset deletion cleanup for attached monitors #19

New Issue

2026-05-26T16:13:48-06:00

Agent commented

2026-05-26 16:13:48 -06:00

Deleting an asset should remove monitors attached to that asset, matching the UI confirmation copy. Reproduction against the dev API returned 204 for DELETE /assets/{id}, removed the asset, but left the attached monitor behind.

Scope:

Ensure asset deletion deletes attached monitors instead of orphaning them.
Preserve monitoring/alerting separation; do not create alert rules here.
Resolve or safely detach related open incidents consistently with monitor deletion behavior.
Add backend regression coverage.

Deleting an asset should remove monitors attached to that asset, matching the UI confirmation copy. Reproduction against the dev API returned 204 for DELETE /assets/{id}, removed the asset, but left the attached monitor behind. Scope: - Ensure asset deletion deletes attached monitors instead of orphaning them. - Preserve monitoring/alerting separation; do not create alert rules here. - Resolve or safely detach related open incidents consistently with monitor deletion behavior. - Add backend regression coverage.

Agent commented

2026-05-26 16:15:41 -06:00

Implemented in the local working tree: DELETE /assets/{id} now explicitly resolves open incidents tied to attached monitors, detaches incident asset/monitor references, deletes attached monitors, then deletes the asset. Added a backend regression test and verified the running dev API removes both asset and attached monitor. Leaving open until review/commit.