Save Background Query Results as Datasets

Turn any Background Query into a durable, queryable dataset you can reuse in Explore, Custom Dashboards, and API requests—without rerunning heavy scans or exporting data.

Save query results as a persistent dataset

When you enable Save results to Dataset on a Background Query, Coralogix writes the query output to a persistent system dataset named system/engine.resultsets.<QUERY_ID>. The dataset is then available everywhere you work—Explore, Custom Dashboards, and APIs—so you can reuse results, join with other sources, visualize, and automate workflows over time.

What you need

To use Background Queries, you must have the LEGACY-ARCHIVE-QUERIES:EXECUTE permission, part of the DataQuerying preset. Find out more about permissions here.

Create & save a Background Query as a dataset

1. Go to Data Flow, then Background Queries, and click New Background Query. Author your query in DataPrime (recommended) or Lucene.
2. In Query Details, turn on Save results to a Dataset.
3. Click Run Background Query.
4. On completion:
   • The card shows Dataset: system/engine.resultsets.<QUERY_ID>.
   • Select Go to Explore to open Explore preloaded with source system/engine.resultsets.<QUERY_ID>.

Query the saved dataset

From Explore, Custom Dashboards, or elsewhere, query any dataset with:

source <dataspace>/<dataset>

Saved Background Query outputs are stored as system datasets under system/engine.resultsets.* and queried like any other dataset, for example:

 source system/engine.resultsets.FCfvKq0bMsZrZgs2hLtQS

Use source system/engine.resultsets.<QUERY_ID> anywhere you can run DataPrime.

Where result datasets appear & how to manage them

Discoverability

Result datasets appear under Data Flow → Dataset Management → System Datasets and are treated as standard system datasets.

Visibility and ingestion

Toggle Write Access (ingest) and Read Access (visibility) per dataset. Changes take effect immediately and persist; disabling read makes the dataset invisible without deleting stored data.

Usage and billing

While system datasets consume units from your daily quota, system/engine.resultsets.* does not consume units. This may be subject to change.

Learn more

• Background Queries — Build & run long‑running queries; API overview.
• Dataspaces — Inheritance, access boundaries, and the system dataspace.
• Datasets — What they are, how to query them (source <dataspace>/<dataset>), writeTo patterns, archived‑data scope.
• Dataset Management — Enable/disable ingestion & visibility controls.