Instrument back-end applications to send spans to Splunk APM 🔗
Instrument your back-end services and applications to send metrics and traces to Splunk Observability Cloud. You can send metrics and traces from back-end applications to Splunk Observability Cloud through the Splunk Distribution of OpenTelemetry Collector, or you can send metrics and traces directly to Splunk Observability Cloud using the API.
flowchart LR
accTitle: Back-end instrumentation diagram
accDescr: OpenTelemetry instrumentation encompasses back-end applications and serverless functions. Instrumentation sends back-end application metrics, traces, and logs to the Splunk Distribution of OpenTelemetry Collector, which sends them to Splunk APM. Instrumentation also sends back-end application metrics, traces, and logs to Splunk APM through the API. Instrumentation sends serverless function metrics, traces, and logs to Splunk APM using the API.
subgraph "\nOpenTelemetry instrumentation"
A["Back-end applications
(Go, Python, Ruby, ...)"]
B["Serverless functions
(AWS Lambda, Azure, GCP)"]
end
A -- "traces, metrics, logs" --> O
O["Splunk Distribution of
OpenTelemetry Collector"]
O --> M["Splunk APM"]
A -- "traces, metrics, logs (API)" --> M
B -- "traces, metrics, logs (API)" --> M
You can instrument applications in each of these languages using official Splunk instrumentation:
To send spans from the Istio service mesh, see Send traces from Istio to Splunk Observability Cloud.
You can also send traces from applications written in languages for which Splunk instrumentation isn’t available:
To learn more about the data collected by Splunk Observability Cloud, see: