-
Notifications
You must be signed in to change notification settings - Fork 162
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
[Custom Threshold Rule] Update the documentation to reflect GA status #3549
Comments
Same question here. Will the change happen in Serverless at the same time as the 8.13 release? |
@bmorelli25 serverless won't have the same date as stateful, as it will be aligned with the PR being merged, then once it's been released to production |
@bmorelli25 @dedemorton, FYI, the linked PR that GA the Custom Threshold rule will be merged today. |
… 🎉 (#176514) ## Summary It closes #172942 by removing the Beta badge. Related to elastic/observability-docs#3549 <img width="579" alt="Screenshot 2024-02-08 at 16 09 12" src="https://github.com/elastic/kibana/assets/6838659/0210f4ed-d788-4041-b0bc-2688996699ff"> ## Release note: We are excited to announce the general availability of the Custom Threshold rule. The Custom Threshold rule is an Observability alerting rule that allows users to define and alert on custom threshold values. The rule can be customized to act on particular data views, using specific aggregations (like sum, average, min, max, percentile, rate, etc.) and via the use of basic math or boolean logic to define the custom thresholds. For more information, please refer to the [user guide](https://www.elastic.co/guide/en/observability/current/custom-threshold-alert.html).
I'm going to move this issue to the current sprint so I can have the PRs up and ready to merge. |
Thanks, @fkanout!
Sounds good, @dedemorton |
… 🎉 (elastic#176514) ## Summary It closes elastic#172942 by removing the Beta badge. Related to elastic/observability-docs#3549 <img width="579" alt="Screenshot 2024-02-08 at 16 09 12" src="https://github.com/elastic/kibana/assets/6838659/0210f4ed-d788-4041-b0bc-2688996699ff"> ## Release note: We are excited to announce the general availability of the Custom Threshold rule. The Custom Threshold rule is an Observability alerting rule that allows users to define and alert on custom threshold values. The rule can be customized to act on particular data views, using specific aggregations (like sum, average, min, max, percentile, rate, etc.) and via the use of basic math or boolean logic to define the custom thresholds. For more information, please refer to the [user guide](https://www.elastic.co/guide/en/observability/current/custom-threshold-alert.html).
… 🎉 (elastic#176514) ## Summary It closes elastic#172942 by removing the Beta badge. Related to elastic/observability-docs#3549 <img width="579" alt="Screenshot 2024-02-08 at 16 09 12" src="https://github.com/elastic/kibana/assets/6838659/0210f4ed-d788-4041-b0bc-2688996699ff"> ## Release note: We are excited to announce the general availability of the Custom Threshold rule. The Custom Threshold rule is an Observability alerting rule that allows users to define and alert on custom threshold values. The rule can be customized to act on particular data views, using specific aggregations (like sum, average, min, max, percentile, rate, etc.) and via the use of basic math or boolean logic to define the custom thresholds. For more information, please refer to the [user guide](https://www.elastic.co/guide/en/observability/current/custom-threshold-alert.html).
Description
In 8.13 the Custom Threshold Rule will be updated from Beta to GA, so the documentation labelling needs to be updated to reflect this status.
Resources
The main issue for the UI changes are in elastic/kibana#172942
The project, that includes links to other tasks, is https://github.com/elastic/actionable-observability/issues/114
Which documentation set does this change impact?
Stateful and Serverless
Feature differences
Same in stateful and serverless
What release is this request related to?
8.13
Collaboration model
The documentation team
Point of contact.
Main contact: @fkanout
Stakeholders:
The text was updated successfully, but these errors were encountered: