Pratik Mankawde bcf2d098d3 fix(telemetry): require https for metrics_endpoint under mTLS ...

With tls_client_cert set, only traces_endpoint was checked for an https
scheme. Telemetry::makeMetricExporter() attaches the client certificate and
key to the metric exporter whenever use_tls=1, and metrics_endpoint defaults
to a plain http URL, so an operator who set up mTLS and overrode only
traces_endpoint exported every metric in the clear with the configured client
identity unused.

Check both endpoints, and state the requirement under metrics_endpoint and
tls_client_cert in the example config. Four config tests cover an explicit
http metrics endpoint, the omitted-key default, both endpoints on https, and
a one-way-TLS control that must stay accepted.

2026-09-09 12:25:17 +01:00

..

validators-example.txt

ci: Add Linux package builds (DEB + RPM) to CI (#6639)

2026-05-16 05:08:37 +00:00

xrpld-example.cfg

fix(telemetry): require https for metrics_endpoint under mTLS

2026-09-09 12:25:17 +01:00