You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit d5fe3ef
Browse filesBrowse the repository at this point in the historyBrowse files
fix: support https for the PromQL remote-write endpoint
CLICKHOUSE_PROMETHEUS_METRICS_ENDPOINT now accepts an http:// or
https:// URL as well as a bare host:port. entrypoint.sh splits off the
scheme and passes it to the prometheusremotewrite exporter through
HYPERDX_PROMETHEUS_SCHEME and HYPERDX_PROMETHEUS_TLS_INSECURE. Both the
standalone and OpAMP-managed configs read these, with defaults that
keep plain HTTP for older collector images.
A bare host:port behaves as before. A path or an unsupported scheme
now fails at startup with a clear error.
fix: support https for the PromQL remote-write endpoint
7
+
8
+
`CLICKHOUSE_PROMETHEUS_METRICS_ENDPOINT` now accepts an `http://` or `https://` URL as well as a bare `host:port`. With `https://`, the collector's `prometheusremotewrite` exporter sends metrics over TLS and verifies the server certificate against the system CAs. Previously the exporter always used plain HTTP, so an HTTPS-only endpoint could not receive metrics. This applies to both standalone and OpAMP-managed collectors.
9
+
10
+
A bare `host:port` keeps plain HTTP, so existing setups are unchanged. The value must not include a path (`/write` is still appended automatically); the collector now exits at startup with a clear error if it does, or if the scheme is anything other than `http` or `https`.
0 commit comments