SPLUNK_REALM currently configures direct ingest endpoints for traces and metrics, but not logs. In src/splunk_otel/distro.py, handle_realm() sets OTEL_EXPORTER_OTLP_TRACES_ENDPOINT to /v2/trace/otlp and OTEL_EXPORTER_OTLP_METRICS_ENDPOINT to /v2/datapoint/otlp, but leaves OTEL_EXPORTER_OTLP_LOGS_ENDPOINT unset.
Profiling data is exported through OTLP logs, so a user who configures SPLUNK_REALM for direct ingest still has to manually set SPLUNK_PROFILER_LOGS_ENDPOINT or OTEL_EXPORTER_OTLP_LOGS_ENDPOINT for profiling logs to go to Splunk Observability Cloud.
Realm handling should also set the logs endpoint, likely /v2/log/otlp, while preserving explicit user-provided endpoint overrides.
SPLUNK_REALM currently configures direct ingest endpoints for traces and metrics, but not logs. In
src/splunk_otel/distro.py,handle_realm()setsOTEL_EXPORTER_OTLP_TRACES_ENDPOINTto/v2/trace/otlpandOTEL_EXPORTER_OTLP_METRICS_ENDPOINTto/v2/datapoint/otlp, but leavesOTEL_EXPORTER_OTLP_LOGS_ENDPOINTunset.Profiling data is exported through OTLP logs, so a user who configures
SPLUNK_REALMfor direct ingest still has to manually setSPLUNK_PROFILER_LOGS_ENDPOINTorOTEL_EXPORTER_OTLP_LOGS_ENDPOINTfor profiling logs to go to Splunk Observability Cloud.Realm handling should also set the logs endpoint, likely
/v2/log/otlp, while preserving explicit user-provided endpoint overrides.