Host Tag & Label Updates to Email Notifications
I appreciate that within the Setup view of a host, I can visually see of my Host Tags with both the TagGroupID:TagID easily visible. With the "Tags of Host" option selected within an Email Notification, it will output just the TagID into the email body. It would be beneficial if the Tag Group ID could be incorporated to the notification because it provides more clarity. Additionally, having the ability to color code them within the email, like they are within the portal would be nice as well. And lastly, having the ability to pick and choose which Host Tags we would like displayed in an email would be nice instead of "all or nothing".
I would also suggest the ability to optionally add Host Labels to the Email body as well.
Comments: 2
-
13 Feb, '23
Jan BaczynskiCustomization options in the email notification are lacking access to important information about context, often stored in host tags and labels.
It would be highly desirable to customize the email rules with everythinh about a host and service state that CheckMK already knows, making generic integrations with all kind of messaging and ticket systems very easy. For a ticket system, tags like device type, criticality, location can not be extracted from $HOSTTAGS$ because the long string can not be parsed reliably or would need separate rules for all possible tag values. Please allow tags to be individually accessible in notification plugins and scripts. Options, best to worst:
1.Allow use of $HOSTTAGS["TagGroupID"]$
2.Always output active tags as key:value pair TagGroupID:TagID via $HOSTTAGS_KV$
3.Send ALL created tag values in CheckMK in fixed order as CSV line with optional header line. Empty tagIDs (e.g. default values from TagGroup) could then be identified correctly by column number -
06 Sep, '23
NicolasI fully agree and this is valid for notifications with custom script too. Having the TagID without the TagGroupID doesn't allow to do proper parsing or value mapping.