Skip to content

Fix separate Alarm Manager events for traditional Syslog alerts - #427

Merged
bmfmancini merged 2 commits into
developfrom
fix/alarmmanager-separate-syslog-events
Oct 26, 2026
Merged

bmfmancini merged 2 commits into
developfrom
fix/alarmmanager-separate-syslog-events

Conversation

@bmfmancini

Copy link
Copy Markdown
Member

Traditional Syslog alerts currently combine all matches from a polling batch into one Alarm Manager occurrence. Submit each match separately so every event has its own hostname, details, count, and stable identity across retries and batch boundaries. Threshold alerts retain their grouped raise/recovery behavior, and any failed submission preserves the existing Syslog notification fallback.

Validation:

  • Full Pest security and unit suite: 540 tests passed, 2,432 assertions, using an isolated Cacti fixture and locked Pest harness.
  • Changed-line coverage: 100% (6/6 executable lines) against develop.
  • Alarm Manager forwarding regression: 55 checks passed.
  • PHP lint and git diff whitespace checks passed.

The runtime adapter was deployed to the requested server and passed all 55 forwarding regression checks there. Fresh provider notification delivery has not been verified. Partial batch acceptance can still trigger the existing aggregate email fallback for the batch.

@sonarqubecloud

Copy link
Copy Markdown

@bmfmancini
bmfmancini merged commit e217789 into develop Oct 26, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants