cx-datasets
Discover the datasets a Coralogix team can query with the `cx datasets` CLI — the fully qualified `<dataspace>/<dataset>` names DataPrime `source` commands need. Use when the user asks to "list datasets", "what datasets do we have", "which datasets can I query", "find datasets", "show dataspaces", "discover datasets", "what data does this team have", "available DataPrime sources", "filter datasets by pillar", "queryable sources", "dataset names for DataPrime", or wants to enumerate or filter the queryable datasets before running a DataPrime query.
How do I install this agent skill?
npx skills add https://github.com/coralogix/cx-cli --skill cx-datasetsIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill facilitates the discovery of Coralogix datasets using the vendor's 'cx' command-line interface. It provides instructions for listing and filtering dataset metadata to ensure accurate DataPrime queries. No security issues or malicious patterns were detected.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Datasets Skill
Coralogix data lives in datasets, addressed as <dataspace>/<dataset> —
e.g. default/logs, default/rum.events, system/labs.limitViolations. Every
DataPrime query starts with source <dataspace>/<dataset>, so before querying
an unfamiliar team (or a source you are not sure exists), list what is actually
queryable instead of guessing names.
CLI Commands
| Command | Purpose | Key flags |
|---|---|---|
cx datasets list | List every dataset queryable by the current profile's team | --filter <DPXL> |
cx datasets list -o json | Same, as a JSON array of dataset rows | - |
- Supports
-p <profile>(repeatable) for multi-profile fan-out; aprofilekey is added to each JSON row when more than one profile is targeted. - Read-only — no
--yesconfirmation needed.
Dataset Row Fields
| Field | Meaning |
|---|---|
dataspace | The dataset's dataspace, e.g. default or system |
dataset | The dataset name inside its dataspace, e.g. logs, rum.events |
pillar | The pillar the data belongs to: logs, spans, data, ... |
entityType | The entity type behind the dataset, e.g. logs, browserLogs/v2, jsonData |
version | The latest dataset version |
teamId | The team that owns the dataset |
Only read-enabled, latest-version datasets are returned. The Source column in
text output is the copy-pasteable source argument.
Workflow
-
List the datasets to see what exists:
cx datasets list cx datasets list -o json | jq -r '.[] | .dataspace + "/" + .dataset' | sort -
Narrow with a DPXL filter when looking for a specific pillar or dataspace:
cx datasets list --filter "<v1> \$d.pillar == 'logs'" cx datasets list --filter "<v1> \$d.dataspace == 'default' && \$d.pillar == 'data'" cx datasets list --filter "<v1> \$d.dataset.contains('rum')" -o json -
Query the dataset with DataPrime, using the full source name:
cx dataprime query --source default/checkoutservice_dataset 'filter $d.severity == ERROR' cx dataprime query --source system/labs.limitViolations 'filter $m.timestamp > now()-1h'--sourceis acx dataprime queryflag —cx logsandcx spansalways query the legacylogs/spansdatasets and take no source override.
DPXL Filter Syntax
--filter takes a DPXL expression including its version tag — it must start
with <v1>. An expression missing the tag is rejected with a 400. In
double-quoted shells (bash/zsh), escape the $ as \$d so the shell does not
expand it — the examples above are copy-paste safe.
Available fields: $d.dataspace, $d.dataset, $d.pillar, $d.entityType,
$d.teamId. Compare with == / != and combine with && / ||. Substring
matching uses method-call syntax — $d.dataset.contains('rum') (case-sensitive
substring), not an infix contains operator.
Key Principles
- Never guess dataset names — a query against a wrong source fails or, worse, silently returns the wrong data. List first, then query.
- The source is
<dataspace>/<dataset>— both parts are needed in DataPrimesourcecommands;default/logsnot justlogs. - Use
-o jsonwithjqwhen you need just the source strings:cx datasets list -o json | jq -r '.[] | .dataspace + "/" + .dataset'. - Filter server-side with
--filterrather than listing everything and grepping locally — same result, less output to parse. - Multi-profile fan-out with
-p <profile>(repeatable) lists datasets across environments in one call.
Related Skills
cx-telemetry-querying— run the DataPrime queries against the datasets discovered here (logs, spans, metrics, RUM).
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/coralogix/cx-cli/cx-datasets">View cx-datasets on skillZs</a>