How to tackle duplicate events when multiple event sources are configured?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-02-2024 03:55 AM
We have few event sources which monitor same systems. One is OOB connector and other is custom one.
For OOB one, the Message key auto generated.
For custom one, the message key us generated via OOB BR "Add message key if missing"
And in this case, the message key is different for same issue.
Hence two different alerts are generated for the same events. How do we handle this event/alert duplicate?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2024 12:53 AM
Anyone?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2024 09:18 PM
Surprised to see no answer 🙂
So looks like there is no solution to this 🤔
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-10-2025 03:51 AM
Anyonee
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-28-2025 01:20 PM
Hi Suggy,
Better late than never. You can create event field mappings or event rules to change your messagekey so both sources have the same messagekey.
For example, you could use the fields Node, Type and resource to recreate a new message key on the alert level that would match on both sources ex : SERVERNAME_Hardware_CPU
Hope it helps
