You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally posted by dwhitehead95 September 27, 2023
We upgraded Splunk to version 9.1(latest) and now our splunk slack alerts are showing our internal default hostname rather than our main splunk url in attached links to alerts. Our internal hostname is unprotected so we need to fix this. I tried specifying the proper url as a param.attachment_results_link in our alert_actions.conf file within the slack_alerts app folder but now the alerts are showing the link I specified rather than a link to the search relevant to the alert setup. How is the view_link variable generated and how can I change it to a desired url while still having the following information that will take the user to the search setup by their alert?
The text was updated successfully, but these errors were encountered:
Previously, I had hostname set within the email stanza and all my links had been showing up fine. After this upgrade, once I defined hostname within the default stanza my links returned to normal.
Discussed in #47
Originally posted by dwhitehead95 September 27, 2023
We upgraded Splunk to version 9.1(latest) and now our splunk slack alerts are showing our internal default hostname rather than our main splunk url in attached links to alerts. Our internal hostname is unprotected so we need to fix this. I tried specifying the proper url as a param.attachment_results_link in our alert_actions.conf file within the slack_alerts app folder but now the alerts are showing the link I specified rather than a link to the search relevant to the alert setup. How is the view_link variable generated and how can I change it to a desired url while still having the following information that will take the user to the search setup by their alert?
The text was updated successfully, but these errors were encountered: