Skip to content

Commit

Permalink
clarify why we are referencing sli in rule docs
Browse files Browse the repository at this point in the history
  • Loading branch information
colleenmcginnis committed Dec 18, 2024
1 parent 53df623 commit 2c53801
Showing 1 changed file with 5 additions and 2 deletions.
7 changes: 5 additions & 2 deletions docs/en/observability/monitor-status-alert.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -234,8 +234,11 @@ image::images/monitor-status-alert-recovery.png[Default recovery message for mon
If you are currently using the Uptime monitor status with a monitor created with Elastic Synthetics,
you should migrate the Uptime monitor status rule to:

* The *Synthetics monitor rule* for <<migrate-monitor-rule-synthetics-rule,synthetic monitor _status_ checks>>.
* The *Synthetics availability SLI* for <<migrate-monitor-rule-synthetics-sli,synthetic monitor _availability_ checks>>.
* If you were using the Uptime rule for *synthetic monitor _status_ checks*,
you can recreate similar functionality using the <<migrate-monitor-rule-synthetics-rule,Synthetics monitor rule>>.
* If you were using the Uptime rule for *synthetic monitor _availability_ checks*,
there is no equivalent in the Synthetics monitor rule. Instead, you can use the
<<migrate-monitor-rule-synthetics-sli,Synthetics availability SLI>> to create similar functionality.

[discrete]
[[migrate-monitor-rule-synthetics-rule]]
Expand Down

0 comments on commit 2c53801

Please sign in to comment.