-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
- This should not pose a problem for generic sources
- Sources can communicate with any endpoint, even switching between them
- Events must therefore be deduplicated
- For this purpose, a unique ID is required for each event
- If one does not exist, one is generated based on the event information
- A job queue is used to ensure that an event is processed only once
- History can also be retrieved via any endpoint, not necessarily the API endpoint that first received the original event
graph LR
subgraph DB [Database]
direction TB
JQ[Job Queue]
H[History]
end
Source((Source))
INA[Icinga Notifications A]
INB[Icinga Notifications B]
%% Connections
Source --> INA
Source --> INB
INA --> DB
INB --> DB
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Todo