Hello, could you clarify where and how proxy settings should be in splunk-launch.conf or somewhere else? Also should we use begin by export?
Also does it takeover other apps specific proxy settings?
Thanks.
splunk-launch.conf works for this, and it's how I'd handle Python-based apps. A few specifics:
HTTPS_PROXY=http://proxy.example.com:3128
HTTP_PROXY=http://proxy.example.com:3128
NO_PROXY=localhost,127.0.0.1,.yourcorp.internalThanks @PickleRick what about splunk-launch.conf?
I've never tried setting those settings there. Common sense suggests that they should get inherited and might be used by python. But I have no experience with it.
There is no single setting which will cause _all_ Splunk components use specified proxy.
Some parts of behaviour (like connecting to splunkbase) can be controlled with the [proxyConfig] section in server.conf (see the specs for server.conf for details).
Some add-ons (especially those using python's requests library) might use environment variables (you could try setting them for systemd unit).
Some add-ons have explicit configuration items for specifying proxy servers.
So it's a bit of hit and miss.