Loading...
Loading...
Compare original and translation side by side
| Command | Purpose |
|---|---|
| List all SLO definitions |
| Get a single SLO by ID |
| Create an SLO from a JSON definition [requires |
| Replace an SLO definition from JSON [requires |
| Delete an SLO [requires |
-o json-p <profile>createupdate--from-file <path>-createupdatedelete--yes| 命令 | 用途 |
|---|---|
| 列出所有SLO定义 |
| 通过ID获取单个SLO |
| 从JSON定义创建SLO [需要 |
| 从JSON替换SLO定义 [需要 |
| 删除SLO [需要 |
-o json-p <profile>createupdate--from-file <path>-createupdatedelete--yes| Field | Meaning |
|---|---|
| Human-readable SLO name |
| Optional description |
| The objective, e.g. |
| |
| Rolling window, e.g. |
| The pillar the SLO is computed from, e.g. |
| 字段 | 含义 |
|---|---|
| 便于人类阅读的SLO名称 |
| 可选描述信息 |
| 目标值,例如 |
| |
| 滚动时间窗口,例如 |
| 计算SLO的支柱类型,例如 |
undefinedundefined
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.
将实时达标率与`targetThresholdPercentage`对比,判断SLO是否正常或是否在消耗错误预算。**基于请求的SLO**衡量正常事件的占比;**基于时间窗口的SLO**衡量正常时间窗口的占比。完成分类后,可切换至`cx-telemetry-querying`技能,在日志、追踪和指标中查找违规的根本原因。getundefinedgetundefined
`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.
`update`和`delete`会报告受影响的告警ID(`effectedSloAlertIds`),请查看该列表——修改或删除SLO可能会禁用与其关联的告警。cx slos getcreateupdatedelete--yesupdatedeleteeffectedSloAlertIds-p <profile>cx slos getcreateupdatedelete--yesupdatedeleteeffectedSloAlertIds-p <profile>cx-alertscx-telemetry-queryingcx-casescx-alertscx-telemetry-queryingcx-cases