coralogix/cx-cli

cx-slos

Manage Coralogix SLO (Service Level Objective) definitions with the cx slos CLI — list and inspect SLOs, check whether targets and error budgets are healthy, and create, update, or delete SLO definitions from JSON.

ソースを見る

使い方

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

開始前の確認

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

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

SLO Management Skill

An SLO (Service Level Objective) defines a reliability target for a service — e.g. "99.9% of requests succeed over 28 days". Use this skill to inspect SLO definitions, judge whether they are healthy, and manage their lifecycle.

CLI Commands

CommandPurpose
cx slos listList all SLO definitions
cx slos get <id>Get a single SLO by ID
cx slos create --from-file <path>Create an SLO from a JSON definition [requires --yes]
cx slos update --from-file <path>Replace an SLO definition from JSON [requires --yes]
cx slos delete <id>Delete an SLO [requires --yes]
  • All commands support -o json for structured output and -p <profile> (repeatable) for multi-profile fan-out.
  • create/update read from --from-file <path>, or - for stdin (the default).
  • create, update, and delete are write operations and require --yes in non-interactive / agent mode.

SLO Definition

The fields surfaced on every SLO:

FieldMeaning
nameHuman-readable SLO name
descriptionOptional description
targetThresholdPercentageThe objective, e.g. 99.9
sloTypeSLO_TYPE_REQUEST (request-based) or SLO_TYPE_WINDOW (window-based)
sloTimeFrameRolling window, e.g. SLO_TIME_FRAME_7_DAYS, SLO_TIME_FRAME_28_DAYS
productTypeThe pillar the SLO is computed from, e.g. SLO_PRODUCT_TYPE_APM

Monitoring SLO Health

bash
# All SLOs with their target and window
cx slos list -o json | jq '[.[] | {name, targetThresholdPercentage, sloType, sloTimeFrame}]'

# Inspect a single SLO in full
cx slos get <slo-id> -o json

Compare the live attainment against targetThresholdPercentage to judge whether the SLO is healthy or burning error budget. A request-based SLO measures the fraction of good events; a window-based SLO measures the fraction of good time windows. After triage, pivot to the cx-telemetry-querying skill to find the root cause of a breach in logs, spans, or metrics.

Creating and Updating SLOs

The safest way to author an SLO is to round-trip an existing one — template from the exact field shape that get returns rather than hand-writing JSON:

bash
# Template from an existing SLO, edit, then create
cx slos get <existing-slo-id> -o json > slo.json
# Edit slo.json: change name, targetThresholdPercentage, sloType, sloTimeFrame, etc.
cx slos create --from-file slo.json --yes

# Replace an existing definition
cx slos update --from-file slo.json --yes

update and delete report the alert IDs they affect (effectedSloAlertIds), so review that list — changing or removing an SLO can disable the alerts attached to it.

Key Principles

  • Check attainment vs. target, not just existence — an SLO at 99.91% against a

99.9% target has almost no error budget left and needs attention before it breaches.

  • Round-trip definitions — template create/update payloads from cx slos get

rather than hand-writing JSON, to keep the exact field shape the API expects.

  • `create`/`update`/`delete` need `--yes` in agent / non-interactive mode.
  • Watch affected alerts — update/delete return effectedSloAlertIds; deleting

an SLO can silence its alerts.

  • Multi-profile fan-out with -p <profile> (repeatable) to compare SLOs across environments.

Related Skills

  • `cx-alerts` — the alert definitions that fire when an SLO's error budget burns.
  • `cx-telemetry-querying` — investigate the logs, spans, and metrics behind an SLO breach.
  • `cx-cases` — triage the cases that group the alert events raised against a service.

タスクに関連する項目

同じリポジトリから

関連する 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日