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.
Once you execute a query, you can view the query metadata when you select the information icon below the query input.
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.
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.
To accelerate threat hunting and incident response, Security Investigator enables you to enrich IP addresses with external reputation data from trusted third-party threat intelligence sources.
Example IP address after enrichment:
To get started, make sure your environment is connected to a supported threat intelligence source. For a list of supported enrichment sources and setup instructions, see Enrich data.
Once you set up and configure an enrichment source, 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.
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.
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 case, allowing for faster triage and correlation.
Looking for more advanced investigation tools?
See Accelerate root cause analysis for a full overview.
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 a security threat.
To start pivoting
In the query results table, right-click on a record.
Go to Pivot results by and select one of the available dimensions.
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.
optional To change the pivoting time range, in the Pivot results by menu, select Customize > 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.
optional To add custom dimensions to pivoting, in the Pivot results by menu, select Customize > Pivot custom dimensions.
Available dimensions are fetched from Grail. You can select a maximum of eight dimensions.
Looking for more advanced investigation tools?
See Accelerate root cause analysis for a full overview.
To select all values in a column
For faster access to data in the results, the Copy option in the query results table menu allows you to copy selected results in different formats, according to your needs.
In the query results table, select what you want to copy (partial or full value of a field, multiple fields, or columns).
Select Copy, then select one of the available format options.
Hover over the available options to display a preview of the output before making a selection.
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 case 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.
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.