Set up Mobile Crash Remediation Agent How-to guide 3-min read Published Jan 28, 2026 Preview Table of contents (Preview) The Mobile Crash Remediation Agent workflow addresses mobile app crashes detected by Dynatrace.
It leverages crash data from Grail and Dynatrace Intelligence to:
Summarize crash impact Identify root causes Suggest fix code snippets You can refine Workflow triggers to focus on critical crashes. The workflow:
Fetches recent crash data using a DQL query Generates concise crash titles Explains details of the crash, including its impact and resolution Creates a troubleshooting document in a notebook , consolidating crash summaries and fixes, and streamlining the remediation process for Android Java app crashes. Prerequisites Dynatrace Intelligence (Preview) app Workflows Get started 1. Set up the workflow trigger Configure the workflow to trigger when Dynatrace detects an increase in mobile app crashes. Refine the trigger filter to focus on critical crashes by adjusting parameters like crash title or impact level. 2. Fetch crash data from Grail Use the following DQL query to retrieve recent crash events:
fetch user.events, scanLimitGBytes: 500 , from: now()-15m, to: now()
| filter characteristics.has_error == true
| filter isNotNull(error.id)
| filter isNotNull(dt.entity.mobile_application)
| filter error.type == "crash"
| sort dt.rum.received_timestamp desc
| limit 3
3. Generate a crash title Utilize Dynatrace Intelligence to create a concise and descriptive title for the detected crash.
4. Analyze the crash and suggest fixes Use Dynatrace Intelligence to summarize the crash impact and root cause in a short paragraph. Automatically generate a suggested fix code snippet for the crash (for example, for Android Java apps). 5. Create a troubleshooting document Automatically generate a Dynatrace Notebook containing the crash summary, root cause explanation, and suggested fix. Attach the notebook to the detected problem for easy access. 6. Monitor and iterate Continuously refine the trigger filters and monitor the workflow’s effectiveness in addressing critical app crashes. Review the suggested fixes and incorporate them into your development process.