Splunk Add-on for Atlassian JIRA Alerts: How to configure the add-on to enable proxy setup?

[ianbow]

Does anyone know how to amend the Splunk Add-on for Atlassian JIRA Alerts to support outbound proxies? We have a public jira instance which can only be access via a proxy and need to fix the code to support this?

[masonmorales · Accepted solution]

If you define the proxy in $SPLUNK_HOME/etc/splunk-launch.conf on the search head, it will use that proxy by default after a Splunk restart.

splunk-launch.conf

NO_PROXY = 127.0.0.1
HTTP_PROXY = 1.2.3.4:9999
HTTPS_PROXY = 1.2.3.4:9999

You can also blacklist any destinations that it should not use a proxy for in the "NO_PROXY" section.

[ianbow]

thanks for the answer as a work around however I believe it would be better to make the python scripts proxy aware? The app is quite old so not too sure if it is still under active development?

[ejwade]

I'm having the same problem. My Splunk server lives in a network that can only leave via an outbound web proxy (squid). @gmelnik, @gmelnik_splunk, @zenmoto, @Anonymous, or @ziegfried - you are all contributors to the git code - are you able to confirm that this add-on is not compatible with the http_proxy setting?