You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The content in the stateful docs should be similar (almost identical) in content and structure to serverless, but unfortunately they have diverged. To better align the docs and address some of the concerns expressed in #2605, we need to change the navigation hierarchy to look something like:
Alerting
Create and manage rules*
Custom threshold
Inventory threshold
Log threshold
Metric threshold
Monitor status
SLO burn rate
TLS certificate
Uptime duration anomaly
View alerts
*check stateful to make sure these names match the UI)
Resources
n/a
Which documentation set does this change impact?
Stateful and Serverless
Feature differences
Some rules that are in stateful are not in serverless, so the navigation will be slightly different across the two docsets.
dedemorton
changed the title
Restructure alerting content to match serverless
Restructure alerting content to be consistent with serverless
Feb 23, 2024
dedemorton
changed the title
Restructure alerting content to be consistent with serverless
Make alerting navigation consistent with serverless
Feb 23, 2024
Description
The content in the stateful docs should be similar (almost identical) in content and structure to serverless, but unfortunately they have diverged. To better align the docs and address some of the concerns expressed in #2605, we need to change the navigation hierarchy to look something like:
*check stateful to make sure these names match the UI)
Resources
n/a
Which documentation set does this change impact?
Stateful and Serverless
Feature differences
Some rules that are in stateful are not in serverless, so the navigation will be slightly different across the two docsets.
What release is this request related to?
N/A
Collaboration model
The documentation team
Point of contact.
Main contact: @dede
Stakeholders:
The text was updated successfully, but these errors were encountered: