coralogix/cx-cli

coralogix-docs

Search and read official Coralogix platform documentation using cx docs search and cx docs fetch.

ソースを見る

使い方

  1. インストールコマンドをコピーし、自分の環境へ導入する前にソースを確認します。
  2. 必要なツール、認証情報、対応環境を原文で確認します。
  3. 入力と成果物を指定し、出力を資料と照合します。
npx skills add https://github.com/coralogix/cx-cli --skill coralogix-docs

開始前の確認

  • 導入にはモデル契約、API枠、ファイルへのアクセス許可は含まれません。
  • スター数や導入数は活動の指標であり、独立した品質・安全性試験ではありません。
リポジトリの原文

見出し、例、コード、表、リンク、参照画像を含む原文を表示しています。

Coralogix docs (cx docs search, cx docs fetch)

These commands read official Coralogix product documentation from coralogix.com/docs. They answer how the platform works and how to configure or use it. They do not query your tenant's logs, spans, metrics, or alerts.

No Coralogix API key is required.

CLI commands

CommandPurpose
cx docs search <query>Find doc pages by keyword. Returns numbered titles + path suffixes.
cx docs fetch <suffix>Download one page as markdown. Pass the suffix from search.

Flags

FlagCommandsDescription
--limitsearchMax results, 1–20 (default 5)
-o json / -o toonbothMachine-readable output

Examples

bash
cx docs search "explore spans" --limit 5
cx docs search "OpenTelemetry traces"
cx docs fetch user-guides/data_exploration/spans/
cx docs search "API keys" -o json

When to use these commands

Use `cx docs search` + `cx docs fetch` when the user wants:

TopicExample questions
UI / workflows"How do I view spans in Coralogix?", "Where is Explore spans?"
Ingestion & integrationsOpenTelemetry setup, agent/collector config, Send Your Data API keys
Platform featuresAlerts, SLOs, dashboards, enrichments, parsing rules, retention
Concepts & architectureHow tracing works, trace-log correlation, data model
Account & accessAPI keys, SSO, roles, regions

Prefer these commands over guessing when the answer depends on current Coralogix product behavior or UI navigation.

When not to use these commands

User needUse instead
Query live logscx logs — cx-telemetry-querying
Query live spans/tracescx spans — cx-telemetry-querying
DataPrime syntax / commandscx dataprime list / cx dataprime show — cx-telemetry-querying
Alerts & cases in the tenantcx alerts, cx cases — cx-alerts, cx-cases
Metrics (PromQL)cx metrics — cx-telemetry-querying
Discover field paths in tenant datacx search-fields

Standard workflow

  1. `cx docs search` with a focused query (2–4 keywords, not full sentences).
  2. Pick the most relevant suffix from the results.
  3. `cx docs fetch` on that suffix.
  4. Answer from the fetched content. Fetch additional pages only when needed.
User: "How do I show spans in the Coralogix website?"

1. cx docs search "explore spans" --limit 5
2. cx docs fetch user-guides/data_exploration/spans/
3. Summarize: Explore → spans dataset → Spans/Traces/Flows tabs → drilldown

Tips

cx docs search

  • Start with 2–4 focused terms, not full sentences.
  • If no matches, try synonyms or broader terms ("tracing" instead of "distributed trace waterfall view").
  • Increase --limit when the first page of hits is ambiguous.
  • Results use path suffixes under /docs/ (not full URLs) — pass them directly to `cx docs fetch`.

cx docs fetch

  • Pass the suffix from `cx docs search` (e.g. user-guides/data_exploration/spans/). Full URLs are rejected.
  • `cx docs fetch` one page at a time — pick the best match first.

Troubleshooting

ProblemAction
No search matchesBroaden or rephrase the query; try feature name + category ("spans UI", "OTel ingestion").
Fetched page is too narrowSearch for the parent topic or run a second search with related terms.
User wants their actual dataSwitch to cx logs, cx spans, cx metrics, or alerts — docs describe the product, not tenant contents.

Related

タスクに関連する項目

同じリポジトリから

関連する Skills

すべての Skills
coralogix
コミュニティ

cx-telemetry-querying

Use this skill for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior", "understand a production incident", "query telemetry data", "look at logs", "search logs", "find errors", "find stack traces", "filter by severity", "check traces", "examine spans", "investigate request latency", "debug service-to-service calls", "look up a trace ID", "analyze RUM data", "query rum.events", "check fro

1時間の導入数
7
GitHub Stars
241
更新日
11月3日
coralogix
コミュニティ

cx-ai-center

Use this skill for any question or action about the user's AI/GenAI applications or agents — their behavior, prompts/responses, quality, hallucinations, guardrails, security, cost/tokens, errors, evaluations/policies, model pricing, or configuration — including comparing or tracking agents over time. It covers both analyzing AI telemetry (GenAI spans) and managing AI Center config via the cx ai-center commands.

1時間の導入数
7
GitHub Stars
233
更新日
10月29日
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時間の導入数
7
GitHub Stars
233
更新日
10月29日
coralogix
コミュニティ

cx-cases

Triage and manage Coralogix Cases with the cx cases CLI — e.g. acknowledge, assign, resolve, or re-prioritize a case, or inspect its event timeline or notification deliveries.

1時間の導入数
7
GitHub Stars
233
更新日
10月29日