Function resolveTarget

apps/host-selfhost/src/telemetry.ts:46–62

(env: Record<string, string | undefined>)

// POST to /v1/traces/v1/traces, which a collector answers with a 404 that never
// reaches the operator — the export just silently produces nothing.
const resolveTarget = (env: Record<string, string | undefined>): TelemetryTarget | undefined => {
  const base = env.OTEL_EXPORTER_OTLP_ENDPOINT?.trim().replace(/\/+$/, "");
  const tracesUrl =
    env.OTEL_EXPORTER_OTLP_TRACES_ENDPOINT?.trim() ?? (base ? `${base}/v1/traces` : undefined);
  if (!tracesUrl) return undefined;
  // Logs are opt-in separately from traces: they are the noisier and more
  // sensitive of the two, carrying every request line and whatever the
  // operator's own log calls hold. Traces answer "where did the time go" by
  // themselves, so shipping logs stays a second, deliberate choice. Set the
  // signal endpoint explicitly if only the traces endpoint is configured —
  // there is no base to derive a logs URL from, and guessing one would export
  // to a path the operator never named.
  const logsUrl = isTruthy(env.EXECUTOR_OTEL_EXPORT_LOGS)
    ? (env.OTEL_EXPORTER_OTLP_LOGS_ENDPOINT?.trim() ?? (base ? `${base}/v1/logs` : undefined))
    : undefined;
  return { tracesUrl, logsUrl, headers: parseHeaders(env.OTEL_EXPORTER_OTLP_HEADERS) };
};

const isTruthy = (value: string | undefined): boolean =>
  value === "1" || value === "true" || value === "yes";