-
Notifications
You must be signed in to change notification settings - Fork 164
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[synthetics] Update monitor status rule docs #4345
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
I've not had a chance to look through this fully, but a couple of comments:
Uptime is not being removed now in 9.0.0. It's still deprecated, but won't be removed until a later date (the release note was updated recently to reflect that change). This deprecated content: whilst it's true that Uptime is deprecated (and as such, the corresponding rule), is this section clear that Uptime is deprecated and the suggestion is to use Synthetics as a whole solution (specifically, is there a chance it could be misread and people think they should use the Synthetics rule if still using Uptime)? |
@colleenmcginnis we don't allow know creating availability alert from status rules, it doesn't make sense as far as i can understand. if you want you can mention Synthetics Availability SLI indicator, that's more suited for that kind of scenerio, where user want to get alerted on availability. So user looking for availability alert can learn about Synthetics Availability SLI indicator. |
You'll need to look at this link ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM , other than if we want to leave a comment about availability condition being replaced with Synthetics Availability SLI !!
[WARNING] | ||
==== | ||
*The Uptime app and the Uptime monitor status rule are deprecated as of version 8.15.0.* | ||
|
||
If you are using the Uptime monitor status rule with the Uptime app, you should migrate the Uptime monitor and the Uptime monitor status rule to Elastic Synthetics and the Synthetics monitor rule. | ||
|
||
If you are using the Uptime monitor status rule with a monitor created with Elastic Synthetics, you should migrate the Uptime monitor status rule to the Synthetics monitor rule. | ||
Learn how in <<migrate-monitor-rule>>. | ||
==== |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did you mean to duplicate this on this page?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added the second note after Paul's comment here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM !!
🚀 Built elastic-dot-co-docs-preview-docs successfully!
|
* document synthetics monitor status rule * document how to move from the uptime rule to the synthetics rule * add code comments * address feedback from @paulb-elastic * add info on using slos for availability * add link * delete table * port to serverless (cherry picked from commit 08cf555) # Conflicts: # docs/en/serverless/serverless-observability.docnav.json
* document synthetics monitor status rule * document how to move from the uptime rule to the synthetics rule * add code comments * address feedback from @paulb-elastic * add info on using slos for availability * add link * delete table * port to serverless (cherry picked from commit 08cf555) # Conflicts: # docs/en/serverless/serverless-observability.docnav.json
…4423) * [synthetics] Update monitor status rule docs (#4345) * document synthetics monitor status rule * document how to move from the uptime rule to the synthetics rule * add code comments * address feedback from @paulb-elastic * add info on using slos for availability * add link * delete table * port to serverless (cherry picked from commit 08cf555) # Conflicts: # docs/en/serverless/serverless-observability.docnav.json * Delete docs/en/serverless directory --------- Co-authored-by: Colleen McGinnis <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
…4424) * [synthetics] Update monitor status rule docs (#4345) * document synthetics monitor status rule * document how to move from the uptime rule to the synthetics rule * add code comments * address feedback from @paulb-elastic * add info on using slos for availability * add link * delete table * port to serverless (cherry picked from commit 08cf555) # Conflicts: # docs/en/serverless/serverless-observability.docnav.json * Delete docs/en/serverless directory --------- Co-authored-by: Colleen McGinnis <[email protected]> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
* document synthetics monitor status rule * document how to move from the uptime rule to the synthetics rule * add code comments * address feedback from @paulb-elastic * add info on using slos for availability * add link * delete table * port to serverless
Description
The Synthetics monitor status rule type was improved in elastic/kibana#186585. This PR makes a few updates to the Create a monitor status rule doc including:
Note: I documented the Uptime and Synthetics rules on the same page titled "Create a monitor status rule" because the "Alerts and rules" dropdown in both the Uptime app and Synthetics UI uses the language "Monitor status rule", but I could be persuaded to document them separately. Either way, starting in 9.0.0, I imagine the Uptime content on this page will go away.
Documentation sets edited in this PR
Check all that apply.
docs/en/observability/*
)docs/en/serverless/*
)docs/en/integrations/*
)Related issue
Closes #4164
Closes #4337
Checklist
Follow-up tasks
Select one.