- Observability: other versions:
- Get started
- What is Elastic Observability?
- What’s new in 8.17
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Add data from Splunk
- Applications and services
- Application performance monitoring (APM)
- Get started
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Manage storage
- Configure APM Server
- Monitor APM Server
- APM APIs
- Troubleshooting
- Upgrade
- Release notes
- Known issues
- 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
- Real user monitoring
- Uptime monitoring (deprecated)
- Tutorial: Monitor a Java application
- Application performance monitoring (APM)
- CI/CD
- Cloud
- Infrastructure and hosts
- Logs
- Troubleshooting
- Incident management
- Data set quality
- Observability AI Assistant
- Reference
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