Splunk Search

Why do the links to searches sent as part of alert emails have the wrong base URL and do not work?

a212830
Champion

Hi,

We've noticed that the link to searches that are sent as part of the alert email are wrong.

The link to the search has "http://mysplunk.com:8000/..."

when it should be "https://mysplunk.com/en-US/..."

As a result, none of the links that are sent with the alert are working.

Tags (4)
0 Karma

chanfoli
Builder

The documentation on the hostname parameter in alert alert_actions.conf is a bit ambiguous on behavior for default ports on http or https but based on the documentation you can use the [protocol://]host.domain.com[:port] format to set the link base, in alert_actions.conf which is presumably what gets edited as Link hostname when you go to settings->general settings->email settings in splunk web.

I would try there or in the config and specify the deisred base in protocol://host.comain.tld format. (e.g. https://splunk.mydomain.com )

See http://docs.splunk.com/Documentation/Splunk/6.2.1/Admin/Alertactionsconf

0 Karma

a212830
Champion

Thanks. I changed them on each server in ../system/local and bounced splunkweb, but it did not take. I use SHP - would it need to be changed somewhere else?

0 Karma

a212830
Champion

Anyone?

0 Karma

chanfoli
Builder

Try running this on your indexers and look for hostname to confirm that alert_actions.conf has been reloaded and that no other location is clobbering your setting :

$SPLUNK_HOME/bin/splunk btool alert_actions list --debug

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...