andrewh
(Andrew)
August 30, 2019, 5:29am
1
I just upgraded from 3.0 to 3.1
Previously we had 2 ways of directly linking to the message that generated an alert:
Under the alert, there was a hotlink to the stream/id of the Message - This has been removed, why would you do this??
The other was using stream_url in an email notification however this no longer seems to work.
jan
(Jan Doberstein)
August 30, 2019, 6:57am
2
if you see a but, or have a feature request, please open one over at github:
Karlis
August 30, 2019, 8:27am
3
Perhaps first make the documentation current, then send users to GH?
http://docs.graylog.org/en/3.1/pages/streams/alerts.html#email-alert-notification
We expose the following objects to the templates.
(…)
stream_url
A string that contains the HTTP URL to the stream.
oshri1091
(Oshri1091)
September 5, 2019, 10:49am
4
It’s didnt work for me too.
can someone help?
i config the server.conf file with the "transport_email_web_interface_url ".
also i make the email alert with ${stream_url}
thanks!
Karlis
September 5, 2019, 12:09pm
5
This is broken in new alerting system, documentation is outdated.
ec10
(Maks)
September 12, 2019, 1:09pm
6
it doesn’t work for us
The check result object for this stream.
check_result.triggeredCondition string representation of the triggered alert condition
check_result.triggeredAt date when this condition was triggered
check_result.resultDescription text that describes the check result
we get blank lines, can someone confirm this?
our template:
Triggered condition:
1: ${check_result.triggeredCondition}
2: ${check_result.triggeredAt}
3: ${check_result.resultDescription}
graylog-server 3.1.1
Karlis
September 12, 2019, 1:45pm
7
From documentation:
check_result
The check result object for this stream.
As previously stated, starting from version 3.1 alerts are not bound to streams, so these objects are invalid and returning nothing.