Maryam Saeidi 7666a4169d [Custom threshold][Alert details page] Deprecate feature flag for Custom threshold rule alert details page (#176666) ... Closes #153867 ## Summary This PR deprecates the following feature flag for the Custom threshold rule alert details page. ``` xpack.observability.unsafe.alertDetails.observability.enabled ```  ## 🧪 How to test - Remove `xpack.observability.unsafe.alertDetails.observability.enabled` from Kibana config - Create a custom threshold rule - Check the alert details page - From alert table's flyout - From action variables - Add `xpack.observability.unsafe.alertDetails.observability.enabled` to the Kibana config - You should see the following warning ``` [WARN ][config.deprecation] You no longer need to configure "xpack.observability.unsafe.alertDetails.observability.enabled". ``` ## Release note - Adds a dedicated alert details page for the Custom threshold rule. When a threshold is breached, the alert details page helps users quickly triage the alert, showing details and context around that alert such as when the alert started, its current status, and other details. When a log rate-based threshold is breached, the alert details page also includes an automatic log rate analysis depicting shared characteristics among log messages contributing to this change and in-context Observability AI Assistant to provide further insight and remedy suggestions.		2024-02-13 17:48:19 -07:00
..
src	[Custom threshold][Alert details page] Deprecate feature flag for Custom threshold rule alert details page (#176666)	2024-02-13 17:48:19 -07:00
index.ts	[RAM] .es-query and .observability.rules.threshold RBAC (#166032)	2023-09-21 15:10:28 -07:00
kibana.jsonc	Update new codeowners for Obs team changes (#170182)	2023-11-08 14:30:17 +00:00
package.json	flag packages without side effects (#173351)	2023-12-19 02:46:39 -07:00
tsconfig.json	[Response Ops][Alerting] Update common component template generation for framework alerts as data (#150384)	2023-02-27 14:24:44 -05:00