- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.15
- 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
- Use OpenTelemetry
- 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
- Multi-factor Authentication
- 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
Explore mobile sessions with Discover
editExplore mobile sessions with Discover
editElastic Mobile APM provides session tracking by attaching a session.id, a guid, to every span and event.
This allows for the recall of the activities of a specific user during a specific period of time. The best way recall
these data points is using Discover. This guide will explain how to do that.
Viewing sessions with Discover
editThe first step is to find the relevant session.id. In this example, we’ll walk through investigating a crash.
Since all events and spans have session.id attributes, a crash is no different.
The steps to follow are:
-
copy the
session.idfrom the relevant document. - Open the Discover page.
-
Select the appropriate data view (use
APMto search all data streams) -
set filter to the copied
session.id
Here we can see the session.id guid in the metadata viewer in the error detail view:
Copy this value and open the Discover page:
set the data view. APM selected in the example:
filter using the session.id: session.id: "<copied session id guid>":
explore all the documents associated with that session id including crashes, lifecycle events, network requests, errors, and other custom events!
On this page