[APM] Add ability to edit APM alerts #76316
Comments
|
Pinging @elastic/apm-ui (Team:apm) |
|
The drawback of deleting and re-creating an alert is that you'll have to get the message first from Another approach I used https://github.com/pmuellr/kbn-action tool to update the existing alert and avoid deleting it. You'll still need to get the alert id from Hope this feature gets in very soon! |
|
We have received user feedback (cc @mikeh-elastic), requesting to allow users to edit APM alerts. As stated in the description, APM alerts are the only ones that do not offer this functionality and there is no workaround at the moment, at least one that would be tolerable from a UX perspective. What is the path forward? (cc @cyrille-leclerc) |
|
Thanks for the feedback all. I've moved this up in priority and I hope we can do that for 7.13. |
|
@sqren @cyrille-leclerc noting the continuous user interest we are receiving for this functionality. |
|
@arisonl thanks for the feedback. We'll prioritize for 7.15 |
By pulling out most of the things that depend on the URL into where we open the flyout and passing them in as metadata props, we can make it so editing rules while in Stack Management. You cannot edit a rule's service name, transaction type, or environment once it has been created (#106786 has been created to allow editing of these other values), but all other values can be edited. In order for useFetcher to work outside of the APM plugin, it has been changed to use useKibana instead of useApmContext for toast notifications. The notifications API from useKibana is slightly different and allows passing a react element instead of a mount point as the body. Fixes #76316.
By pulling out most of the things that depend on the URL into where we open the flyout and passing them in as metadata props, we can make it so editing rules while in Stack Management. You cannot edit a rule's service name, transaction type, or environment once it has been created (elastic#106786 has been created to allow editing of these other values), but all other values can be edited. In order for useFetcher to work outside of the APM plugin, it has been changed to use useKibana instead of useApmContext for toast notifications. The notifications API from useKibana is slightly different and allows passing a react element instead of a mount point as the body. Fixes elastic#76316.
By pulling out most of the things that depend on the URL into where we open the flyout and passing them in as metadata props, we can make it so editing rules while in Stack Management. You cannot edit a rule's service name, transaction type, or environment once it has been created (#106786 has been created to allow editing of these other values), but all other values can be edited. In order for useFetcher to work outside of the APM plugin, it has been changed to use useKibana instead of useApmContext for toast notifications. The notifications API from useKibana is slightly different and allows passing a react element instead of a mount point as the body. Fixes #76316. Co-authored-by: Nathan L Smith <nathan.smith@elastic.co>
By pulling out most of the things that depend on the URL into where we open the flyout and passing them in as metadata props, we can make it so editing rules while in Stack Management. You cannot edit a rule's service name, transaction type, or environment once it has been created (elastic#106786 has been created to allow editing of these other values), but all other values can be edited. In order for useFetcher to work outside of the APM plugin, it has been changed to use useKibana instead of useApmContext for toast notifications. The notifications API from useKibana is slightly different and allows passing a react element instead of a mount point as the body. Fixes elastic#76316.
Generic alerts, metrics alerts, and Uptime alerts can be edited directly in the Alerting and Actions menu of Kibana: Select edit to open the edit flyout panel.
Alerts created from the APM app do not offer this option. The only workaround I can find is to delete the alert and manually recreate it. It'd be great to be able to edit APM alerts.
The text was updated successfully, but these errors were encountered: