Repository navigation
Handle aggregate node alerts without parser failures #5566
Description
🤖 Generated by the Agentic Engineer
An aggregate node event can identify its kind without naming one node. The alert-maintenance lifecycle matcher applies a regular expression to the absent name before checking the complete event shape. A synthetic reproduction emits a null-value parser error while the surrounding script still exits successfully.
Handle this input without extending any alert exemption. The unreviewed aggregate event must remain visible, and every existing exact match and negative control must retain its result.
Acceptance:
- Add a regression that reproduces the parser error with a node event that has no name.
- Require the expected name shape before evaluating a node-name expression, without converting an unknown event into an approved match.
- Preserve named-node, mixed-event and near-miss controls, with no parser stderr for the aggregate case.
- Validate the protected delivery and observe a subsequent scheduled run without this parser error before closing.
Part of #4981
Metadata
Metadata
Assignees
Labels
No labels
Type
Fields
Priority
Medium
Effort
Low
Projects
- Status
Activity
chore: agent-claim #5566 nonce=2de30d44bd61b352395e686594845010
devantler commentedon Oct 29, 2026
Delivered through #5574 at
098140e7a37ec652a83792e006574f844be8a167. The protected deployment and post-merge validation passed.The subsequent 12:00 UTC scheduled run completed successfully with command and arguments identical to the reviewed render and no parser error. Its completed Job and Pod identities, exit status and complete logs were verified and retained privately. The unnamed aggregate regression remains visible, with named-node and near-miss controls preserved; no alert exemption was extended.
This satisfies the parser issue's acceptance criteria. Platform-wide stabilization remains open.