Problem investigation mode
- Latest Dynatrace
- Explanation
- 3-min read
- Published Jun 03, 2026
Problem investigation mode maintains continuity between applications, keeping you focused on the relevant problem for as long as your investigation requires.
Overview
When you drill down to 
Logs from 
Problems or from another application with Problem investigation mode enabled, Logs opens in Problem investigation mode. Your problem context is preserved: the same query, filters, and timeframe from the source are applied automatically, so you see the relevant log records without any manual setup.
Problem badge
While Problem investigation mode is active, a Problem badge appears in the top bar of Logs, showing the current problem ID (for example, Problem: P-1234567890). From the badge's menu, you can explain the problem or reset the timeframe to the problem timeframe.
Query and filters
The query and filters from the source context are applied automatically when Logs opens. You see the log records that were in scope at the time of the drill-down.
You can adjust the timeframe, query, or filters to explore further. The Problem badge will remain after you make these adjustments, but the log records displayed may no longer match the original filters.
Timeframe
The timeframe is inherited from the source context:
- From the Problems View logs drill-down: The timeframe is the problem timeframe plus an offset.
- From another application (for example,
Kubernetes): The timeframe is the application's current timeframe, which may differ from the problem timeframe plus the offset.
To reset the timeframe to the problem timeframe plus offset, select the Problem badge > Reset the problem timeframe.
Problem context
As you navigate between Logs and other apps that support Problem investigation mode, the problem context is preserved in both directions. The destination app opens with:
- The related entity or trace context.
- The timeframe from Logs or the originating application.
- A Problem badge for the same problem.
Exit Problem investigation mode
To exit Problem investigation mode, select (Exit problem investigation) on the Problem badge.
Exiting removes the Problem badge. Your filters and timeframe remain as they were.
Use cases
You can use Problem investigation mode in Logs to:
- Investigate logs relevant to a specific problem with context already applied. There's no need to reapply query or filters.
- Adjust the timeframe or filters to explore beyond the original problem scope while keeping the problem context visible.
- Drill down to related entities or traces while preserving the problem context in the target application.
- Exit Problem investigation mode to continue free-form log exploration.
Related topics
LogsLog Analytics