Reporting

How do I change the URL used in email alerts

imacdonald2
Path Finder

Currently links to reports that are emailed out contain just the hostname, not the fully qualified machine name. Our build standard is command host should return just the hostname and host -f returns hostname.fqdn.com. I have set serverName in /opt/splunk/etc/system/local/server.conf to hostname.fqdn.com but the links still come out using hostname

Tags (3)
1 Solution

cnk
Path Finder

By links to reports do you mean alert emails? For alert emails you can set the hostname option in alert_actions.conf.

alert_actions.conf.spec

hostname = <string>
    * Sets the hostname used in the web link (url) sent in alerts.
    * This value accepts two forms.
       * hostname
        examples: splunkserver, splunkserver.example.com
       * protocol://hostname:port
        examples: http://splunkserver:8000, https://splunkserver.example.com:443
    * When this value is a simple hostname, the protocol and port which
      are configured within splunk are used to construct the base of
      the url.
    * When this value begins with 'http://', it is used verbatim.  
      NOTE: This means the correct port must be specified if it is not
      the default port for http or https.
    * This is useful in cases when the Splunk server is not aware of
      how to construct an externally referencable url, such as SSO
      environments, other proxies, or when the Splunk server hostname
      is not generally resolvable.
    * Defaults to current hostname provided by the operating system, or if that fails "localhost".
    * When set to empty, default behavior is used.

HTH

View solution in original post

cnk
Path Finder

By links to reports do you mean alert emails? For alert emails you can set the hostname option in alert_actions.conf.

alert_actions.conf.spec

hostname = <string>
    * Sets the hostname used in the web link (url) sent in alerts.
    * This value accepts two forms.
       * hostname
        examples: splunkserver, splunkserver.example.com
       * protocol://hostname:port
        examples: http://splunkserver:8000, https://splunkserver.example.com:443
    * When this value is a simple hostname, the protocol and port which
      are configured within splunk are used to construct the base of
      the url.
    * When this value begins with 'http://', it is used verbatim.  
      NOTE: This means the correct port must be specified if it is not
      the default port for http or https.
    * This is useful in cases when the Splunk server is not aware of
      how to construct an externally referencable url, such as SSO
      environments, other proxies, or when the Splunk server hostname
      is not generally resolvable.
    * Defaults to current hostname provided by the operating system, or if that fails "localhost".
    * When set to empty, default behavior is used.

HTH

Get Updates on the Splunk Community!

A Guide To Cloud Migration Success

As enterprises’ rapid expansion to the cloud continues, IT leaders are continuously looking for ways to focus ...

Join Us for Splunk University and Get Your Bootcamp Game On!

If you know, you know! Splunk University is the vibe this summer so register today for bootcamps galore ...

.conf24 | Learning Tracks for Security, Observability, Platform, and Developers!

.conf24 is taking place at The Venetian in Las Vegas from June 11 - 14. Continue reading to learn about the ...