Try it free

Manage results

  • Latest Dynatrace
  • How-to guide

See below how you can grasp information from the DQL query response in a structured and viable way.

Wrap lines

You can view longer log lines without horizontal scrolling with the Enable line wrap option. You can perform this action from the query results table menu without executing a query.

Example view when line wrapping is disabled (content1) and enabled (content2):

line wrap
line wrap
  1. In the query results table menu, select the column header for the field you are interested in.

  2. Select Enable line wrap.

    To reverse this action, select Disable line wrap.

View multiline logs

For a better understanding of data, you can view the multiline logs like stack traces with their line breaks and tabulation in their original form with the Enable multiline option. You can perform this action from the query results table without executing a query.

Example view when multiline is disabled (content1) and enabled (content2):

multiline
multiline
  1. In the query results table menu, select the column header for the field you are interested in.

  2. Select Enable multiline.

    To reverse this action, select Disable multiline.

View query metadata

After you execute a query, the Metadata tab next to Results and Chart shows details about the query execution.

  1. Execute a query.

  2. Above the results table, select the Metadata tab.

    The Metadata tab of the query results shows the query metadata, the scanned buckets with their match ratio, and the canonical query.
    The Metadata tab of the query results shows the query metadata, the scanned buckets with their match ratio, and the canonical query.

The tab contains the following sections:

  • Query metadata: statistics about the execution, such as when the query ran (Executed at), the analysis timeframe (Analysis from and Analysis to), Query ID, Execution time, Scanned records, Scanned bytes, Timezone, and Response size.

    • Next to Query ID, select the copy button to copy the ID.
    • Next to Analysis from or Analysis to, select to copy the start time, end time, or the whole timeframe, or to add the timeframe to your custom timeframes.
  • Scanned buckets: the Grail buckets that the query read, sorted by the amount of scanned data. For each bucket, you can see the table, the scanned data volume (Scanned), and the share of records that matched your query (Matched and Match). Select the copy button next to a bucket name to copy it.

  • Canonical query: the normalized form of your query as Grail executed it.

  • Metadata as JSON: expand this section to view the complete raw metadata.

Notifications about the query result are also displayed on this tab. When a notification appears above the results, select it to open the Metadata tab.

To find out which data a slow or unexpected query read, check Scanned buckets and Scanned bytes.

Enhance queries

You can group and aggregate records with the same value for a given field with the Summarize option, available from the query results header menu or from the record details window. Selecting this option modifies the current query and adds the summarize command to the query input.

Explore data in the original format

  • With the View field details option, you can examine the data in its original format, regardless of the content, and without horizontal scrolling, even if it contains non-printables like tabs, multiple spaces, or line breaks. Investigations Investigations recognizes and formats popular data structures like JSON, making it easier to read in the field details view.
  • With the View record details option, you can display a single selected record in a pivoted way. All fields are displayed vertically, thus saving you time from horizontal scrolling and enabling faster access to the data.

Example field view

  • Data in a field:

    Field before inspecting
    Field before inspecting
  • Data in a field upon viewing details:

    field upon inspecting
    field upon inspecting

Example record view

  • Data in a record:

    record before inspecting
    record before inspecting
  • Data in a record upon viewing details:

    record upon inspecting
    record upon inspecting

How to view details

In the query results table, right-click on a field and select View field details or View record details.

  • To view record details, you can also double-click on any record in the query results table, or select a cell and press Enter.
  • You can use keyboard arrows (or arrows in the record details window) to navigate between records: you don't have to close the window to open the next record; just use your keyboard.
view details
view details

Selecting one of these options opens the field or record details window. From there, your investigation is supported with further options such as filter, extract fields, open in other apps, add evidence, and add fields.

In the record details window, right-click a field to access actions for that field:

  • Right-click a field name in the Key column to add the field to the query (:PlusIcon: Add field) or to summarize by it.
  • Right-click a value in the Value column to filter, copy, or add it to an evidence list.

View Smartscape details

When a result field contains a Smartscape ID (for example, HOST-1234567890ABCDEF), you can inspect the Smartscape node without leaving Investigations Investigations.

  1. In the query results table or in the record details window, right-click a Smartscape ID value.

  2. Select SmartScape details.

    The action is disabled if the value isn't a Smartscape ID.

    Right-clicking a Smartscape ID in the results table opens a menu with the SmartScape details action.
    Right-clicking a Smartscape ID in the results table opens a menu with the SmartScape details action.

In the window that opens:

  • The Details tab lists all fields of the Smartscape node. Right-click a field to view its details.
  • The Connected nodes tab (with the number of connected nodes) shows a graph of the nodes related to the selected node. Hover over a node or connection in the graph to see its properties.
  • Select View in Smartscape to open the node's related nodes in the Smartscape app in a new browser tab.

Find keywords in results

To locate specific text in the current query results without changing the query, use the keyword search above the results table.

  1. Above the results table, select the Find keywords field, or press Cmd/Ctrl+Shift+F.

  2. Enter one or more keywords.

    • Separate keywords with spaces to match records that contain any of the keywords.
    • Wrap several words in double quotes to search for them as one phrase, for example, "failed login".
  3. Press Enter to jump to the first matching record. Press Enter again to go to the next match.

    Matches are highlighted in the results table and in the field and record details windows.

    The Find keywords field above the results table highlights each match of the keyword in the results.
    The Find keywords field above the results table highlights each match of the keyword in the results.

The search affects only how results are displayed. While a keyword search is active, a message above the results offers Add to query, which adds the keywords to your query as a search command.

Keep matches visible in long cells

If a keyword matches text far into a long cell, Investigations Investigations trims the cell so that the match stays visible. Next to the trimmed text, use Show more context and Show less context to reveal more or less of the text before the match.

A long cell is trimmed around the matched keyword, with buttons to show more or less surrounding context.
A long cell is trimmed around the matched keyword, with buttons to show more or less surrounding context.

Highlight keywords from the query

You can also highlight the text values that your query itself searches for or filters on, for example "my-host" in filter host == "my-host".

  • To turn on highlighting, in the settings in the upper-right corner of the page, turn on Highlight keywords from DQL query. You can also press Cmd/Ctrl+B to toggle it.

Highlighting is off by default. For more settings, see Settings.

For keyboard shortcuts for the results table, see Keyboard shortcuts.

Enrich IP addresses

To accelerate threat hunting and incident response, Investigations Investigations enables you to enrich IP addresses with external reputation data from trusted third-party threat intelligence sources.

Example IP address after enrichment:

enrichment-report
enrichment-report

Before you begin, configure an enrichment connection (for example, AbuseIPDB, VirusTotal, or any custom HTTP‑based threat‑intelligence API).

Once configured, you can:

  • Manually enrich individual IP addresses

  • Enable automatic enrichment for evidence list entries

Manual enrichment

You can manually enrich IP addresses directly from your investigation results.

  1. Right-click any IP address in the results table.

  2. Select Enrich IP.

  3. Choose your configured enrichment source (for example, AbuseIPDB or VirusTotal).

Saving an enriched IP to the evidence list preserves its enrichment data for consistent access throughout your investigation. To revisit the details, select the details icon next to the enriched IP address.

click for report details
click for report details

If you select several IP addresses, Investigations Investigations enriches them in parallel.

If the enrichment source can't be reached, an Enrichment failed message informs you about the connection error. Try again or choose another connection.

Manual enrichment is ideal when reviewing specific indicators of compromise (IoCs) or validating suspicious activity.

Automatic enrichment

To streamline your workflow, you can enable automatic enrichment for your evidence lists.

  1. In Evidence lists, toggle Automatic enrichment to On for any item in your target list.

  2. Choose the enrichment connection you want to apply.

This configuration applies to the entire evidence list. Every IP address you add will be automatically enriched using the selected source.

Set default automatic enrichment

To enable automatic enrichment by default for new investigations, set the default modes and connection in the settings.

  1. In the upper-right corner of the page, select the settings .
  2. Go to Enrichment settings.
  3. Under Default auto-enrichment modes, turn on Auto-enrich all items added to Suspicious list, Auto-enrich all items added to Safe list, or Auto-enrich all items added to custom IP list.
  4. Under Default enrichment connection, select the connection to use. Select Edit connection to open the connection settings.

The defaults apply to the IP evidence lists of new investigations. You can override them for an individual evidence list in the Auto-enrich menu of that list.

The Enrichment settings show the switches for automatic enrichment of evidence lists and the default enrichment connection.
The Enrichment settings show the switches for automatic enrichment of evidence lists and the default enrichment connection.

Need help managing your evidence list? See Manage evidence for step-by-step guidance.

New IP addresses added to the evidence list are enriched automatically using your selected source. Each enriched IP includes a details icon for quick access to its reputation data—no tool-switching required.

Automatically enriched IP addresses are tagged and stored with your investigation, allowing for faster triage and correlation.

Looking for more advanced investigation tools?
See Accelerate root cause analysis for a full overview.

Create and use lookup tables

You can define lookup tables from query results or by uploading files. Lookup tables are stored in Grail and can be reused across investigations to enrich queries with contextual data.

Creating, viewing, and deleting lookup tables requires the storage:files:read, storage:files:write, and storage:files:delete permissions.

Define from query results

To save investigation results as a lookup table

  1. Do one of the following:

    • In your DQL results, right-click the relevant records and select Create lookup table from the context menu.
    • In the left-hand panel, go to the Grail storage tab, select New lookup table file, and then select From results to use all results of the current query, or From selection to use only the records you selected.
  2. In the wizard that opens:

    • Select the columns to include in the lookup table
    • Define the lookup field and table path
    • Optional Add a display name and description to help identify the table
  3. Select Create to save the table in Grail.

Define by uploading a file

To upload external reference data

  1. In the left-hand panel of an opened investigation, go to the Grail storage tab, select New lookup table file, and then select From file.

  2. In the wizard that opens:

    • Select a file from your disk
    • Define a DPL pattern to create columns for the lookup table
    • Specify a lookup field and table path
    • Optional Add a display name and description to help identify the table
  3. Select Create to save the table in Grail.

When you create a table with the path of an existing lookup table, you're asked to confirm that you want to overwrite it.

Use and manage lookup tables

Once saved, lookup tables appear in the Lookup tables (/lookups/…) section of the Grail storage tab in the left-hand panel of Investigations Investigations. Use the search field to find a table by name.

To use or manage a table

  1. Select the table.

  2. Select an action from the menu:

    • Load: open the table in a new query node using the load command.
    • Append: append the table to your current query.
    • Lookup: add a lookup command to your current query.
    • Join: add a join command to your current query.
    • Delete: remove the table from Grail.

For more about how lookup data works in Grail, see Lookup data in Grail.

Pivot results

With the query pivoting function, you can instantly navigate through and analyze interconnected data from any record based on the available dimensions. This allows you to save time from manual query creation and speed up your investigation.

For example, you start with a query to view errors from several cloud applications and pivot to a specific pod from where the specific error originated to get more context. This approach provides insights into relationships between events and helps uncover hidden patterns and anomalies that could indicate performance issues, operational irregularities, or security threats.

To start pivoting

  1. In the query results table, right-click on a record.

  2. Go to Pivot query by and, under Built-in entity dimensions, select one of the available dimensions (for example, Host, Trace id, or Kubernetes pod).

    Dimensions that the record has no value for are disabled.

    This creates a query node that fetches logs for the specific entity within a +/- five-minute range of the original log record.

    The node from where pivoting was triggered remains unchanged.

    To pivot by a dimension that isn't listed, select View all built-in dimensions, select a dimension in the window that opens, and then select Pivot query.

  3. Optional To change the pivoting time range, in the Pivot query by menu, select Pivot settings and set Pivot time range.

    You can modify the pivoting time range at any time during your investigation from the settings menu in the upper-right corner of the page.

Pivot with custom dimensions

If the built-in dimensions don't fit your data, pivot with your own DQL query.

  1. In the query results table, right-click a field value and go to Pivot query by.

  2. Select Use custom dimensions.

    The New custom pivot window opens. If you selected several records, each value becomes a separate pivot query.

  3. In the Query editor tab, write the DQL query for the pivot, or select an existing dimension from Custom dimensions. Use the placeholders listed under Available macros:

    • $value is replaced with the field values from your chosen records. The query must contain it at least once.
    • $from and $to are replaced with the start and end of the pivoting time range around the record's timestamp.
  4. Optional In the Manage values tab, add, edit, or remove the values to pivot on.

  5. Optional To reuse the query later, select Save as custom dimension, enter a Display name for dimension, and select Save. If you changed a saved dimension, select Update custom dimension to overwrite it, or Save as new custom dimension to keep the original.

  6. Select the pivot button, which shows the number of queries (for example, Pivot 3 queries).

    If the pivot creates more than five nodes, you're asked to confirm.

To edit or delete saved custom dimensions, or to add a new one, go to the settings > Pivot settings > Custom dimensions. The DQL editor in this form resizes with the settings window.

The New custom pivot window shows a multi-line pivot query and a button that pivots all four selected values at once.
The New custom pivot window shows a multi-line pivot query and a button that pivots all four selected values at once.

Pivot query by evidence

You can also pivot from the items in your evidence lists to see where an indicator appears in your data.

  1. In the Evidence lists section, do one of the following:

    • Select next to an evidence list and select Pivot query by evidence to pivot on all items in the list.
    • Select next to a single item and select Pivot query by evidence to pivot on that item.
    • Open an evidence list, select items, and select the Pivot query by evidence button.

    The Pivot query by evidence window opens with a query that searches for the evidence value ($value).

  2. Optional Adjust the query in the Query editor tab, or change the evidence values in the Manage values tab.

  3. Select the pivot button (for example, Pivot 4 queries).

    Investigations Investigations creates one query node per evidence item.

The evidence list menu offers the Pivot query by evidence action to create pivot queries from the items in the list.
The evidence list menu offers the Pivot query by evidence action to create pivot queries from the items in the list.

Looking for more advanced investigation tools?
See Accelerate root cause analysis for a full overview.

Select the whole column

To select all values in a column

  1. In the query results table menu, select the column header for the field you are interested in.
  2. Select Select column.
select a column
select a column

Select cells and navigate with the keyboard

You can move through the query results table and open details without the mouse.

  • Use the arrow keys to move the selected cell up, down, left, or right.
  • Press Cmd/Ctrl and the up or down arrow key to jump 10 rows.
  • Press Enter to open the record details of the selected record.

Keyboard navigation works when the focus is on the results table and no details window is open. For all shortcuts, see Keyboard shortcuts.

Copy results in various formats

For faster access to data in the results, the Special copy option in the query results table menu allows you to copy selected results in different formats, according to your needs. To copy a single value as it appears, select Copy value.

  1. In the query results table, select what you want to copy (partial or full value of a field, multiple fields, or columns).

  2. Select Special copy, then select one of the available format options:

    • Selection as text: the part of the text that you highlighted with the mouse.
    • Field as text (Fields as text for several fields): the field values. With several fields selected, Fields as text with header includes the column names.
    • Field as DQL value (Fields as DQL value): the values formatted as DQL literals, ready to paste into a query.
    • Record as DQL (Records as DQL): the complete records as a DQL data command.
    • Record as JSON (Records as JSON) and Record as CSV (Records as CSV): the complete records in the respective format.

    Hover over the available options to display a preview of the output before making a selection.

    After selecting several records with the Shift key, the Special copy menu lists the formats in which you can copy them.
    After selecting several records with the Shift key, the Special copy menu lists the formats in which you can copy them.

To copy without opening a menu, select the cells and press Cmd/Ctrl+C to copy the field values (tab-separated), or Alt+C to copy the selected records as DQL. These shortcuts work when the focus is on the results table and no text is selected.

Correlate logs with performance metrics

To assess incident impact faster and uncover root causes with greater precision, you can seamlessly correlate log records with performance metrics. This enables faster troubleshooting, enhanced visibility, and more proactive resolution.

To view and correlate performance metrics with your log data

  1. Right-click any log record in your results table to access available metric keys based on metadata.

  2. Select View performance metrics, then select the desired metric (for example, CPU or memory utilization).

    This displays a metric chart in the right pane, next to Evidence.

    performance metrics
    performance metrics

Chart behavior and context awareness

  • A red vertical line marks the timestamp of the selected log record, helping you correlate metric fluctuations with specific events. The red line won't be shown if the selected timestamp falls outside the chart's timeframe.

  • As you navigate other log records or query nodes, the chart updates dynamically to maintain context across your investigation.

  • The chart remains visible and consistent throughout your investigation—even when switching between query nodes—as long as the selected log record contains a timestamp within the defined timeframe.

Timeframe logic

  • By default, the chart displays metric data within a +/- 15-minute window around the log record's timestamp. To change the window, in the settings , go to Performance metrics and set Default timespan (15 min, 30 min, 1 hour, 2 hours, or 1 day).
  • If no timestamp is available in the log record, the query's analysis timeframe is used to generate the metric chart.
  • You can manually redefine the timeframe to suit your investigation.

Entity dimensions and metric types

  • The default metric dimension is dt.source_entity. If it's missing, other entity fields, such as container, pod, and host, are used.

  • If no entity is available, the Performance metrics menu is disabled.

  • You can select from available dimensions in the dropdown menus and switch between metrics such as CPU, memory, network, or load.

Chart actions

Use the chart to move from a metric spike back to the matching log records.

  • Act on a single data point: select a data point to access the following actions.

    • Select results: select the log records in the results table that fall within the data point's interval.
    • Set as reference time: use the middle of the data point's interval as the reference time of your investigation.
  • Act on a time range: drag across the chart to select a range, then select one of the following actions.

    • Select results from timeframe: select the log records in the results table that fall within the range.
    • Add to custom timeframes: save the range as a custom timeframe.
    • Filter or Filter out: add a timestamp filter for the range to your query.
    • Fetch logs from timeframe: create a query node that fetches the logs of the charted entity for the range.
  • Use the chart menu: select in the upper-right corner of the chart for the following actions.

    • Copy DQL: copy the DQL query behind the chart.
    • Fetch logs from timeframe: create a query node from the chart's DQL query. Hover over the action to preview the query.
    • Refocus to origin node: return to the query node where you opened the chart.
    • View entity details: view the entity fields that the chart is based on.
    • Clear: close the chart.

Looking for more advanced investigation tools?
See Accelerate root cause analysis for a full overview.

Visualize with charts

Once you execute a query, if the results can be visualized as a chart, the Chart option becomes available next to Results.

Example charts:

  • Line charts

    line chart
    line chart

    Running a timeseries or using makeTimeseries command instantly displays a line chart with the resulting data.

  • Bar charts

    bar chart
    bar chart
  • Pie charts

    pie chart
    pie chart

You can configure the charts display in Chart > Options.

Related topics

  • Threat hunting and forensics
  • DPL Architect
  • Notebooks
  • Dynatrace Query Language
  • Use DQL queries
  • DQL commands
  • DQL functions
  • DQL operators
  • DQL data types
  • Conversion and casting functions
  • DQL selection and modification commands
Related tags
Threat Observability