- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.14
- Get started
- Observability AI Assistant
- Application performance monitoring (APM)
- Self manage APM Server
- Data Model
- Features
- Navigate the APM UI
- Perform common tasks in the APM UI
- Configure APM agents with central config
- Control access to APM data
- Create an alert
- Create and upload source maps (RUM)
- Create custom links
- Filter data
- Find transaction latency and failure correlations
- Identify deployment details for APM agents
- Integrate with machine learning
- Explore mobile sessions with Discover
- Observe Lambda functions
- Query your data
- Storage Explorer
- Track deployments with annotations
- OpenTelemetry integration
- Manage storage
- Configure
- Advanced setup
- Secure communication
- Monitor
- APM Server API
- APM UI API
- Troubleshoot
- Upgrade
- Release notes
- Known issues
- Log monitoring
- Infrastructure monitoring
- AWS monitoring
- Azure monitoring
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Uptime monitoring
- Real user monitoring
- Universal Profiling
- Alerting
- Service-level objectives (SLOs)
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
APM version 8.13
editAPM version 8.13
editAPM version 8.13.2
editNo significant changes.
APM version 8.13.1
editNo significant changes.
APM version 8.13.0
editAdded
edit-
map OTel’s
span.Status: Unsettoevent.outcome: successinstead ofevent.outcome: unknown12199 - Add support for Otel code.stacktrace 12096
-
http.request.body.bytesnow reports the bytes read from request body even if Content-Length is -1 12451 -
Use
messaging.systemandmessaging.operationto detect OTel messaging span for transactions 12506 -
Add support for OTel data stream routing by parsing
data_stream.datasetanddata_stream.namespacefrom: (from lowest to highest precedence) resource attributes, instrumentation scope attributes, and signal-level attributes. This is a breaking change only for users relying on the existingdata_streamattributes being stored as labels. 12578 -
Map OTel transaction
elastic.profiler_stack_trace_idsattribute 12493 - Reduce go-docappender error logging verbosity. Groups all errors by groups and reports a new "document" field 12604
Was this helpful?
Thank you for your feedback.