I am testing with a brand new install of a clustered Sensu Go (5.15.0).
Current problem: Assets are not downloaded due to HTTP_PROXY not being used.
I found several postings on that and entered HTTP_PROXY=http://my.proxy.host:port into /etc/default/sensu-backend or /etc/sysconfig/sensu-backend (I am on CentOS 7).
Result: sensu-backend does not finish starting, only etcd is started (to be seen by list of open ports).
Adding a NO_PROXY list does not remedy that.
Just entered HTTPS_PROXY into /etc/sysconfig/sensu-backend. Now sensu-backend is starting up fine, but it does not use the proxy for https connections to assets.bonsai.sensu.io:
error getting assets for event: error fetching asset: Get https://assets.bonsai.sensu.io/68546e739d96fd695655b77b35b5aabfbabeb056/sensu-plugins-cpu-checks_4.0.0_centos_linux_amd64.tar.gz: dial tcp 184.108.40.206:443: i/o timeout
I tried to find a way to download the asset manually and feed the tar.gz file into sensu-backend, but so far I came up empty.
Is this possible as a workaround?