Other data ingestion methods 🔗
This section describes alternative ways of getting custom metric data into Splunk Observability Cloud.
Monitor AWS Lambda functions 🔗
Use the Splunk OpenTelemetry Lambda Layer to instrument your lambdas on AWS to send traces and metrics to Splunk Observability Cloud.
The SignalFx Lambda wrappers are deprecated. To learn how to migrate to the Splunk OpenTelemetry Lambda Layer, see Migrate from SignalFx Lambda wrappers to Splunk OpenTelemetry Lambda Layer.
Send data points using REST APIs 🔗
The application also supports an extensive REST API that enables you to send data points to Infrastructure Monitoring. See an example of how to send data points using the curl command in Observability Cloud REST APIs for sending data points.
Send metrics using client libraries 🔗
Splunk Infrastructure Monitoring offers client libraries for Java, Python, Ruby, Go, and node.js. Use the libraries to send metrics from your code to Splunk Observability Cloud. See SignalFlow client libraries for more information.
Use the upstream OpenTelemetry Collector 🔗
You can use the upstream OpenTelemetry Collector instead of Splunk Distribution of OpenTelemetry Collector. The following list describes the differences in each version:
No packaging or installer scripts for Linux and Windows
No configuration management using Ansible or Puppet
No configuration sources
No Smart Agent capabilities
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).
Do the following to use the upstream OpenTelemetry Collector:
Use the OpenTelemetry Collector contribution. This contribution includes components that are vendor specific.
Configure the upstream OpenTelemetry Collector.
Example configurations 🔗
See Set the host.name attribute override using the OpenTelemetry Helm chart for an example of how to get the correct number of hosts on Kubernetes.