Problem Statement
We generally deploy hyperdx in kubernetes and have separate local agents (k8s daemonsets) for each signal type (vector for logs, otel for others) each having a separate OTLP endpoint.
Hyperdx allows setting the OTLP endpoint for Hyperdx's own telemetry by setting the env vars OTEL_EXPORTER_OTLP_ENDPOINT for the backend app and NEXT_PUBLIC_OTEL_EXPORTER_OTLP_ENDPOINT for the frontend app. But there is to specify separate endpoints per signal.
Proposed Solution
We would like to be able to set separate endpoints per signal type like:
OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
OTEL_EXPORTER_OTLP_LOGS_ENDPOINT
NEXT_PUBLIC_OTEL_EXPORTER_OTLP_TRACES_ENDPOINT
NEXT_PUBLIC_OTEL_EXPORTER_OTLP_METRICS_ENDPOINT
NEXT_PUBLIC_OTEL_EXPORTER_OTLP_LOGS_ENDPOINT
This alligns with the Otel conventions: https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter
Problem Statement
We generally deploy hyperdx in kubernetes and have separate local agents (k8s daemonsets) for each signal type (vector for logs, otel for others) each having a separate OTLP endpoint.
Hyperdx allows setting the OTLP endpoint for Hyperdx's own telemetry by setting the env vars
OTEL_EXPORTER_OTLP_ENDPOINTfor the backend app andNEXT_PUBLIC_OTEL_EXPORTER_OTLP_ENDPOINTfor the frontend app. But there is to specify separate endpoints per signal.Proposed Solution
We would like to be able to set separate endpoints per signal type like:
This alligns with the Otel conventions: https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter