Scheduled Reports
Run a saved search or dashboard on a cron schedule and produce downloadable CSV and self-contained HTML report artifacts.
Schedule a saved search or dashboard to produce downloadable report artifacts. You can prepare recurring investigation summaries, dashboard snapshots, and compliance exports without rerunning the source manually.
Creating a report
Start from a search or a dashboard
- From search — open the search More (…) menu → Schedule report. Your current query is carried into the report. You can also schedule any saved query directly from the saved-queries palette.
- From a dashboard — use the dashboard viewer's overflow menu.
Configure the report
The editor opens as a right-side flyout:
| Field | Meaning |
|---|---|
| Name | How the report appears in the Reports list and in notifications |
| Source query | The nPL query (or dashboard) the report runs — editable, including when editing an existing report |
| Time window | The lookback each run covers (e.g. the last 24 hours) |
| Schedule | Cron expression controlling when runs execute |
| Runs to keep | Retention — how many past runs (and their artifacts) are kept |
| Enabled | Toggle the schedule on/off without deleting the definition |
Save and verify the first run
After the first scheduled run completes, open the report's run history and download the artifact to confirm the output is what you expect.
Artifacts
| Report source | Artifacts produced |
|---|---|
| Search | A CSV of the results plus a self-contained HTML summary |
| Dashboard | A self-contained HTML report |
Artifacts contain no external assets — everything is embedded — so they render correctly in air-gapped deployments and when forwarded outside the SOC.
Artifacts are stored and downloadable in-app. Each run records its status, row count, and truncation flags: row and size caps are enforced and flagged on the run, never silently applied — if a report was cut off, the run says so. Old runs are pruned to the report's runs to keep retention.
Notifications on completion
When a run completes you're notified through:
- The in-app bell.
- The notification spine — completion fires a
report_readyevent. Subscribe a channel to the Scheduled reports event type (see Notifications) to route report cards to Slack, Teams, or a generic webhook.
Execution identity
Report runs execute as the report owner, under the owner's access — the results reflect what that user is allowed to see, not what the person reading the artifact can see.
Managing reports
The Reports management surface lists all report definitions, each report's run history (status, row count, truncation), and artifact downloads for every retained run. Use the Enabled toggle to pause a schedule without losing its history.
Troubleshoot
Need help with these checks? Contact support with the affected deployment, request ID and time with timezone.
An audit report has no rows
Queries for the internal audit log (metadata.log_source=audit) return no rows without an interactive audit-view context. Review audit data interactively.
A report is incomplete
Check the run’s row and size truncation flags. Reports enforce caps and record when they truncate results.
A report card has no link
Set the notification base URL in Settings → Notifications.
What's next
Dashboards
Build nano dashboards by hand, from search results or with the AI wizard: chart types, drilldown, variables, auto-refresh, sharing and troubleshooting.
Prevalence Tracking
Find rare hashes, domains and IPs by how many of your hosts have seen them, stamped on each event at ingest and computed on demand with prevalence.