Other data ingestion methods 🔗
If your needs are not covered with OpenTelemetry instrumentation, you can still send data to Splunk Observability Cloud using the following alternative methods.
Send data using the REST API 🔗
Observability Cloud supports an extensive REST API that lets you send data points and events. This is useful when you need to bypass the Collector. See an example in Observability Cloud REST APIs for sending traces and metrics.
Send custom metrics 🔗
You can send custom metrics to Observability Cloud, for example to instrument a service that isn’t supported yet. To create and send custom metrics, see Send custom metrics to Splunk Observability Cloud.
Send traces using the gRPC endpoint 🔗
You can send trace data in OTLP format directly to Observability Cloud using the gRPC endpoint, either directly or from an OpenTelemetry Collector. See Send traces to Splunk Observability Cloud using the gRPC endpoint.
Send metrics using client libraries 🔗
To send metrics from your code to Observability Cloud, you can use several client libraries for Java, Python, Ruby, Go, and Node.js. See SignalFlow client libraries for more information.
Use the upstream OpenTelemetry Collector 🔗
You can use the upstream OpenTelemetry Collector instead of the Splunk Distribution of OpenTelemetry Collector. For more information on the differences between the Splunk distribution and the upstream version, see Upstream OpenTelemetry Collector.
Splunk only provides best-effort support for the upstream OpenTelemetry Collector. Only Splunk OpenTelemetry distributions are in scope for official Splunk support and support-related service-level agreements (SLAs).