Grafana Data Source Proxies: CloudWatch and Infinity

A dashboard loading in your browser does not establish that Grafana's backend can reach the data source. Start with the failing data-source check and the plugin making that outbound request.

Find the plugin's route selector

For CloudWatch, enable per_datasource_http_proxy_enabled in Grafana's aws configuration to expose the data source's HTTP proxy settings. The documented choices include using HTTP_PROXY, HTTPS_PROXY and NO_PROXY, or entering a proxy URL in the data-source settings.

For Infinity, open its Network options. Select the environment-based proxy, no proxy, or an explicit proxy URL. The explicit mode has separate username and password fields when needed.

For another plugin, look for its supported proxy interface; Grafana's implementation language does not establish that interface.

Check where the selected value comes from

If you choose the environment, put the variables on the Grafana service or container performing the request. Exporting them in a terminal after the service has started does not update that running process.

If you choose an explicit URL, use the proxy listener's actual protocol and an address reachable from the backend. For a publicly reachable data source where public proxies are permitted, the HTTP proxy list is a source of candidate endpoints. Set intended exceptions for internal destinations. Run the data-source check again and use its first connection or authentication error to decide what to inspect next.