1. Describe your incident: Notifications does not seem to be able to parse anything ${message.*}-related except for ${message.message}, so other variables such as ${message.cluster_name} or ${message.namespace_name} are completely ignored, thus making our received emails with aggregated messages a …

I found it wonky to work with too, try ${message.fields.<fieldname>} I wonder if anyone has done a writeup or video on the how and why building alert message code ids more difficult than it needs to be … or at least seems that way. :smiley:

Hi @tmacgbay ${messages.fields.container_name} worked. Thanks so much! Best,

[image] tmacgbay: ${message.fields.}. Oh boy, I need fix that post. Looks like my copy & paste malfunctioned.

hey @m_mlk Sorry about that post you copied from, it was incorrect. Also have you seen these? Adding Stream URL to Notification Template ALERT template - HTML

hi @gsmith no worries mate. I figured it out and the alerts work now as expected. Nope, I haven’t taken a look at the other 2 links but thanks for sharing. I will keep them in mind if needed.

[SOLVED] message.cluster_name is ignored for notifications

Graylog Central (peer support)

gsmith (GSmith) November 19, 2022, 5:59am 5

hey @m_mlk

Sorry about that post you copied from, it was incorrect.

Also have you seen these?

Adding Stream URL to Notification Template
ALERT template - HTML

Topic		Replies	Views
${message.message} not working in the alert template Graylog Central (peer support)	16	6343	September 18, 2018
Notifications don't contain data Graylog Central (peer support) alert	3	273	November 15, 2023
Events using aggregation group by field removes data from notification Graylog Central (peer support)	11	547	March 27, 2024
Problem with create alerts Graylog Central (peer support)	9	5949	September 17, 2017
"count()" var in Graylog Alert Notifications Graylog Central (peer support)	0	521	January 22, 2021

[SOLVED] message.cluster_name is ignored for notifications

Related topics