Saltar al contenido
Marketplace

cx-slos

de coralogix

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. Use when the user asks to "list SLOs", "check SLO status", "is an SLO breaching", "error budget", "create an SLO", "update an SLO", "delete an SLO", or "service level objective".

Resumen

SKILL.mdLeída en 233692c

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

# 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:

# 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.

Archivos 1 archivo

Instálala a mano

Deska ejecuta esto por ti, para cada agente que elijas. Para ejecutarlo tú en una terminal:

npx skills add coralogix/cx-cli --skill cx-slos

Más de coralogix

  • cx-telemetry-queryingcoralogixUse 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 frontend performance", "frontend errors", "Core Web Vitals", "JavaScript exceptions", "query metrics", "check CPU usage", "run a PromQL query", "check error rate", "look up a metric", "check memory usage", "how do I write a DataPrime query", "DataPrime syntax", or wants to answer questions using observability data from logs, metrics, traces, RUM, or APM.3,700 instalaciones en skills.sh0
  • cx-alertscoralogixThis 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.2,900 instalaciones en skills.sh0
  • cx-search-dashboardcoralogixThis skill should be used when the user asks to "find a dashboard", "search dashboards", "does a dashboard exist for X", "find widgets that query Y", "which dashboards use this field", "find a dashboard about errors", "look up dashboards by description", "search for existing monitoring dashboards", "find widgets that reference a field", or wants to discover existing Coralogix dashboards or widgets using natural-language or field-based search.2,900 instalaciones en skills.sh0
  • coralogix-docscoralogixSearch 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.2,800 instalaciones en skills.sh0
  • cx-cost-optimizationcoralogixUse this skill when the user asks to "check data usage", "list TCO policies", "reduce Coralogix costs", "optimize observability spend", "lower our logging bill", "data budget exceeded", "TCO policy", "retention tier", "archive storage", "ingestion costs", "frequent search vs archive", "why is our bill so high", "spending too much on logs", "data retention settings", "cost analysis", "usage breakdown", "optimize log volume", "control data ingestion", "archive cold data", "billing units", "plan consumption", "daily plan", "overage", "PAYG", "usage anomaly", "usage trend", "cx_data_usage_units", or wants to investigate, analyze, or reduce Coralogix data costs.2,700 instalaciones en skills.sh0
Todas las skills de coralogix