Event management not generating message key automatically
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-11-2020 06:55 AM
Hi All,
I am pushing event using API explorer and get everything working as I expect but when i see in event's "message_key" field then I don't find any auto generated message key when i do not provide this value in API explorer.
I do not get message key generated in event record but I do get it in Alert's "message_key" field.
Any idea what can be wrong?
Thanks
- Labels:
-
Event Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2020 05:16 AM
If my answer is correct please mark it correct so others can easily find the answer. Thank you.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2020 08:01 AM
Robert is correct, there is a BR on the em_alert table called "Add message key if missing" which concatenates fields together to make our own message_key ::
addMessageKey();
function addMessageKey(){
current.message_key = current.source + "_" + current.node + "_" + current.type.name + "_" + current.resource;
}

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2020 01:15 AM
FYI, all of my events from PRTG do have message_key assigned.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2020 05:16 AM
Yes which makes sense cause certain pull/push integrations will provide that to be used as it's typically a unique key on the generating side.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-12-2020 08:21 AM
Hi,
Message if not passed is auto generated with combination of 4 fields on event record using the BR ROB told.
This is the field which is mainly used for alert correlation in first place.
Thanks,
Ashutosh