.conf25 registration is now open!Register today

 Send APM traces

You can send spans and traces to Splunk Observability Cloud using the trace ingest API endpoints. This is useful, for example, when you must bypass or can't use the Splunk OpenTelemetry Collector, or when instrumenting an application for which there is no official instrumentation available.

The following instructions show how to use the API to send traces to APM. For the API reference, see Send APM Traces.

Info Circle

When you send an API request, you need to use the endpoint specific to your organization's realm. To learn more, see Realms in endpoints.

 Requirements

 Spans formats

You can send spans and traces in the following formats:

FormatContent-TypeEndpoint
Zipkin JSON1 and JSON2application/jsonhttps://ingest.<realm>.signalfx.com/v2/trace/signalfxv1
Jaegerapplication/x-thrifthttps://ingest.<realm>.signalfx.com/v2/trace/jaegerthrift
Splunk APM Protocol (SAPM)application/x-protobufhttps://ingest.<realm>.signalfx.com/v2/trace/sapm
OpenTelemetry Protocol (OTLP)application/x-protobufhttps://ingest.<realm>.signalfx.com/v2/trace/otlp

 Use the API to send traces

To learn how to send traces, see the POST /v2/trace and the POST /v2/trace/otlp reference topics in Splunk Observability Cloud API reference.

 Send traces over gRPC

The gRPC ingest endpoint for traces is ingest.<realm>.signalfx.com:443, where <realm> is your Splunk Observability Cloud realm. Requests must contain an access token in the X-SF-Token header.

To obtain an access token, see Organization access tokens.

To find the realm name of your account, follow these steps:

  1. Open the navigation menu in Splunk Observability Cloud.
  2. Select Settings.
  3. Select your username.

The realm name appears in the Organizations section.