Files
pulse/internal/alerts
rcourtman ec8b88fe27 Resolve docker alert resource IDs in Patrol scope resolution
Have Patrol investigate on a Docker container or host alert returned
patrol_scope_unresolved because alerts publish docker:<host>/<container>
and docker:<host> identities while patrol runtime records only carried
unified IDs, raw container IDs, and names. Register the alert-form
identities as known scope aliases on docker host and container records,
exporting the alerts helper so the format cannot drift between the two
subsystems. The automatic alert-fired patrol path sends the same
identity, so scoped runs it triggered for docker alerts were failing
resolution the same way.

Refs discussion #1699

Contract-Neutral: behavioral bug fix refs discussion 1699: patrol scope resolution could not resolve docker alert resource IDs; no public contract delta
2026-08-14 06:26:15 +01:00
..
2026-03-18 16:06:30 +00:00
2026-03-18 16:06:30 +00:00
2026-03-18 16:06:30 +00:00
2026-03-18 16:06:30 +00:00
2026-03-18 16:06:30 +00:00
2026-07-24 15:46:56 +01:00
2026-03-18 16:06:30 +00:00