Skip to content

note on the possibility of duplicate alerts #487

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 26, 2025
Merged

note on the possibility of duplicate alerts #487

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d0b493c
note on the possibility of duplicate alerts
DaanHoogland Mar 11, 2025
c4ff61f
Apply suggestions from code review
DaanHoogland Mar 11, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions source/adminguide/events.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,14 @@ machine on the event bus. All the CloudStack events (alerts, action
events, usage events) and the additional category of resource state
change events, are published on to the events bus.

.. note::
Alerts for some more important events will be sent multiple
times. This is due to the nature of guarding
certain resources from multiple threads in the code, to make sure
that events are not missed. Examples are "Host down" or
"HA starting VM". These are considered too important to not send
immediately and hence a check if they are already queued can not be done.

Implementations
~~~~~~~~~~~~~~~
An event bus is introduced in the
Expand Down