coralogix/cx-cli

cx-datasets

Discover the datasets a Coralogix team can query with the cx datasets CLI — the fully qualified / names DataPrime source commands need.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/coralogix/cx-cli --skill cx-datasets

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

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

CommandPurposeKey flags
cx datasets listList every dataset queryable by the current profile's team--filter <DPXL>
cx datasets list -o jsonSame, as a JSON array of dataset rows-
  • Supports -p <profile> (repeatable) for multi-profile fan-out; a profile

key is added to each JSON row when more than one profile is targeted.

  • Read-only — no --yes confirmation needed.

Dataset Row Fields

FieldMeaning
dataspaceThe dataset's dataspace, e.g. default or system
datasetThe dataset name inside its dataspace, e.g. logs, rum.events
pillarThe pillar the data belongs to: logs, spans, data, ...
entityTypeThe entity type behind the dataset, e.g. logs, browserLogs/v2, jsonData
versionThe latest dataset version
teamIdThe 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

  1. List the datasets to see what exists:
bash
   cx datasets list
   cx datasets list -o json | jq -r '.[] | .dataspace + "/" + .dataset' | sort
  1. Narrow with a DPXL filter when looking for a specific pillar or dataspace:
bash
   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
  1. Query the dataset with DataPrime, using the full source name:
bash
   cx dataprime query --source default/checkoutservice_dataset 'filter $d.severity == ERROR'
   cx dataprime query --source system/labs.limitViolations 'filter $m.timestamp > now()-1h'

--source is a cx dataprime query flag — cx logs and cx spans always query the legacy logs/spans datasets 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

DataPrime source commands; default/logs not just logs.

  • Use `-o json` with `jq` when you need just the source strings:

cx datasets list -o json | jq -r '.[] | .dataspace + "/" + .dataset'.

  • Filter server-side with --filter rather 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).

같은 저장소의 Skills

더 많은 Skills

모든 Skills
coralogix
커뮤니티

coralogix-docs

Search and read official Coralogix platform documentation using cx docs search and cx docs fetch. Use when the user asks how Coralogix features work, how to configure or use the UI, set up integrations (OpenTelemetry, agents, collectors, webhooks), manage API keys, explore spans/traces/logs in the product, configure alerts/SLOs/dashboards, or needs authoritative product docs — not live tenant telemetry.

1시간 설치 수
2
GitHub Stars
243
업데이트
11월 17일
coralogix
커뮤니티

cx-alerts

This skill should be used when the user asks to "manage alerts", "create alert", "list alerts", "delete alert", "check alert status", "enable alert", "disable alert", "investigate firing alerts", "check which alerts are active", "find alerting rules", "set up an alert", "configure alerting", "mute an alert", "silence an alert", "see alert definitions", "check alert priority", or wants to manage Coralogix alert definitions using the cx CLI.

1시간 설치 수
2
GitHub Stars
243
업데이트
11월 17일
coralogix
커뮤니티

cx-cli

This skill should be used whenever the user runs any cx command, uses the cx CLI, Coralogix CLI, or mentions cx in the context of Coralogix observability. This skill provides cross-cutting concerns like update notifications that apply to all cx commands.

1시간 설치 수
2
GitHub Stars
243
업데이트
11월 17일
coralogix
커뮤니티

cx-dashboards

Build and deploy a Coralogix dashboard for a given service from its logs, spans, metrics, and service specs. Discovers telemetry via cx CLI commands, emits importable Coralogix JSON, verifies every PromQL and DataPrime query live through the cx CLI, and creates or updates dashboards via cx dashboards create and cx dashboards replace. Use whenever the user asks to create, build, generate, deploy, update, replace, or modify a Coralogix dashboard, monitoring dashboard, or observability dashboard fo

1시간 설치 수
2
GitHub Stars
243
업데이트
11월 17일