Skip to content

fix(sc-event): replay status-change events after a downtime ends#345

Draft
sdepassio wants to merge 1 commit into
developfrom
CTOR-2043-stream-connector-do-not-send-alerts-that-happened-during-a-downtime-when-downtime-ends
Draft

fix(sc-event): replay status-change events after a downtime ends#345
sdepassio wants to merge 1 commit into
developfrom
CTOR-2043-stream-connector-do-not-send-alerts-that-happened-during-a-downtime-when-downtime-ends

Conversation

@sdepassio
Copy link
Copy Markdown
Contributor

Description

When a status change during a downtime, the event is never sent to the stream connector.
Fix: the last status event is stored, and if at the end of the downtime the status has changed the event is sent.

Fixes CTOR-2043

Type of change

  • Patch fixing an issue (non-breaking change)
  • New functionality (non-breaking change)
  • Breaking change (patch or feature) that might cause side effects breaking part of the Software

Checklist

Community contributors & Centreon team

  • I have followed the coding style guidelines provided by Centreon
  • I have commented my code, especially new classes, functions or any legacy code modified. (docblock)
  • I have commented my code, especially hard-to-understand areas of the PR.
  • I have rebased my development branch on the base branch (master, maintenance).

@sdepassio sdepassio force-pushed the CTOR-2043-stream-connector-do-not-send-alerts-that-happened-during-a-downtime-when-downtime-ends branch from 6de8b1c to 585cbc5 Compare May 5, 2026 12:44
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.

1 participant