Data stream routing
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is generally available and ready for production usage. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is generally available and ready for production usage. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Generally available
Stack
Generally available
Elastic APM supports routing APM data to user-defined data stream names using the reroute processor. However, you can also ingest OTLP data without having to create new ingest pipelines.
To automatically route OTLP data, set the data_stream.dataset and data_stream.namespace attributes. These attributes map to the respective ECS fields.
You can set the data_stream attributes at resource level, scope level, and record level. Elastic parses the attributes in increasing order of precedence. For example, record data_stream attributes override the scope data_stream attributes. This implies that data_stream attributes are inherited from previous levels. If a scope does not specify data_stream attributes, it uses the resource attributes.
For guidance on how to set resource attributes in OpenTelemetry, refer to setting resource attributes.