Monitor and troubleshoot playbook automations with XQL datasets
Monitor and troubleshoot Cortex XDR playbook automations by using XQL datasets and automation logs to identify execution issues and analyze results.
Cortex XDR provides centralized visibility into playbook executions and their automation logs. Use XQL datasets to monitor performance, investigate workflow failures, and analyze activity across playbooks, scripts, and commands.
Monitor automation health with dashboards
You can use XQL datasets to build dashboards that expose the operational health of your SOC's automation. For example, you can monitor:
Execution frequency: Track how often specific playbooks (such as malware handling workflows) are triggered to understand load and frequency.
Success vs. failure rates: Create widgets to visualize the percentage of successful runs versus failures across all automation.
Trigger attribution: Use the
trigger_by_typeandexecuted_byfields to identify if automation is being driven primarily by system rules, scheduled jobs, or manual analyst intervention.
Troubleshoot playbooks and scripts
When automation workflows fail or behave unexpectedly, XQL allows you to isolate the root cause. For example, you can:
Identify broken scripts: If multiple playbooks are failing, use the
playbook_tasksorscripts_and_commands_metricsdatasets to check if a specific script version (such as an Okta reset password script) is consistently returning errors across different parent workflows.Analyze task failures: Filter the
playbook_tasksdataset bytask_statusto find tasks that are stuck in a pending state or failing. Review theretry_countand standardized error fields to determine if failures are due to transient network issues or configuration errors.Sub-playbook visibility: Use the
investigation_idandparent_playbook_idfields to trace the execution flow of complex, nested playbooks.
Implement performance best practices
Use duration metrics to optimize your automation and reduce system resource consumption.
Monitor execution time: Analyze the
durationandnet_durationfields in theplaybook_runsdataset to identify playbooks that are taking an unusually long time to complete.Identify heavy tasks: Use
execution_time_secsin theplaybook_tasksdataset to find specific tasks that are slowing down your workflows.Standardized error handling: Transition away from the deprecated
erroranderrorsfields to use standardized error reporting to ensure consistent troubleshooting across all datasets.
Access automation datasets
To review automation logs and execution metadata, run an XQL query against the relevant dataset in the Query Center.
Automation dataset field reference
The following tables list the key fields for the datasets supporting monitoring and troubleshooting automations.
XQL query use cases
The following query examples show how to quickly access automation metrics and troubleshoot issues.
Identify failed playbook runs
Find the top 10 slowest playbooks (by average runtime)
Find the slowest tasks (by average duration)
Identify which automation scripts are used most
Last updated
Was this helpful?
