See below how you can grasp information from the DQL query response in a structured and viable way.
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):

In the query results table menu, select the column header for the field you are interested in.
Select Enable line wrap.
To reverse this action, select Disable line wrap.
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):

In the query results table menu, select the column header for the field you are interested in.
Select Enable multiline.
To reverse this action, select Disable multiline.
After you execute a query, the Metadata tab next to Results and Chart shows details about the query execution.
Execute a query.
Above the results table, select the Metadata tab.

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.
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.
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.
Investigations recognizes and formats popular data structures like JSON, making it easier to read in the field details view.Data in a field:

Data in a field upon viewing details:

Data in a record:

Data in a record upon viewing details:

In the query results table, right-click on a field and select View field details or View record 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:
When a result field contains a Smartscape ID (for example, HOST-1234567890ABCDEF), you can inspect the Smartscape node without leaving
Investigations.
In the query results table or in the record details window, right-click a Smartscape ID value.
Select SmartScape details.
The action is disabled if the value isn't a Smartscape ID.

In the window that opens:
To locate specific text in the current query results without changing the query, use the keyword search above the results table.
Above the results table, select the Find keywords field, or press Cmd/Ctrl+Shift+F.
Enter one or more keywords.
"failed login".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 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.
If a keyword matches text far into a long cell,
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.

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".
Highlighting is off by default. For more settings, see Settings.
For keyboard shortcuts for the results table, see Keyboard shortcuts.
To accelerate threat hunting and incident response,
Investigations enables you to enrich IP addresses with external reputation data from trusted third-party threat intelligence sources.
Example IP address after enrichment:

Before you begin, configure an enrichment connection (for example, AbuseIPDB, VirusTotal, or any custom HTTP‑based threat‑intelligence API).
Once configured, you can:
You can manually enrich IP addresses directly from your investigation results.
Right-click any IP address in the results table.
Select Enrich IP.
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.

If you select several IP addresses,
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.
To streamline your workflow, you can enable automatic enrichment for your evidence lists.
In Evidence lists, toggle Automatic enrichment to On for any item in your target list.
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.
To enable automatic enrichment by default for new investigations, set the default modes and connection in the 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.

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.
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.
To save investigation results as a lookup table
Do one of the following:
In the wizard that opens:
Select Create to save the table in Grail.
To upload external reference data
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.
In the wizard that opens:
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.
Once saved, lookup tables appear in the Lookup tables (/lookups/…) section of the Grail storage tab in the left-hand panel of
Investigations. Use the search field to find a table by name.
To use or manage a table
Select the table.
Select an action from the menu:
load command.lookup command to your current query.join command to your current query.For more about how lookup data works in Grail, see Lookup data in Grail.
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
In the query results table, right-click on a record.
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.
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.
If the built-in dimensions don't fit your data, pivot with your own DQL query.
In the query results table, right-click a field value and go to Pivot query by.
Select Use custom dimensions.
The New custom pivot window opens. If you selected several records, each value becomes a separate pivot query.
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.Optional In the Manage values tab, add, edit, or remove the values to pivot on.
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.
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.

You can also pivot from the items in your evidence lists to see where an indicator appears in your data.
In the Evidence lists section, do one of the following:
The Pivot query by evidence window opens with a query that searches for the evidence value ($value).
Optional Adjust the query in the Query editor tab, or change the evidence values in the Manage values tab.
Select the pivot button (for example, Pivot 4 queries).
Investigations creates one query node per evidence item.

Looking for more advanced investigation tools?
See Accelerate root cause analysis for a full overview.
To select all values in a column

You can move through the query results table and open details without the mouse.
Keyboard navigation works when the focus is on the results table and no details window is open. For all shortcuts, see Keyboard shortcuts.
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.
In the query results table, select what you want to copy (partial or full value of a field, multiple fields, or columns).
Select Special copy, then select one of the available format options:
data command.Hover over the available options to display a preview of the output before making a selection.

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.
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
Right-click any log record in your results table to access available metric keys based on metadata.
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.

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.
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.
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.
Act on a time range: drag across the chart to select a range, then select one of the following actions.
Use the chart menu: select in the upper-right corner of the chart for the following actions.
Looking for more advanced investigation tools?
See Accelerate root cause analysis for a full overview.
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

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

Pie charts

You can configure the charts display in Chart > Options.