-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[APM] Editing APM alerts via Generic Alerting UI is not possible #65399
Labels
enhancement
New value added to drive a business result
Team:APM
All issues that need APM UI Team support
Comments
smith
added
bug
Fixes for quality problems that affect the customer experience
Team:APM
All issues that need APM UI Team support
labels
May 5, 2020
Pinging @elastic/apm-ui (Team:apm) |
sorenlouv
changed the title
Editing existing alerts created in APM is broken
[APM] Editing APM alerts via Generic Alerting UI is not possible
May 13, 2020
@smith Should this be closed or updated since this is no longer a bug but an enhancement? |
sorenlouv
added
enhancement
New value added to drive a business result
and removed
bug
Fixes for quality problems that affect the customer experience
labels
May 13, 2020
This should be closed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
New value added to drive a business result
Team:APM
All issues that need APM UI Team support
A flyout open and then disappears and the screen goes blank.
This is in the JS console:
This is because we're passing in a component that's not wrapped with the needed context provider when we create the alert.
It should bring up the flyout and allow you to edit and save the alert.
We've opened #65549 with the Alerting team in order to make it so the edit action can be disabled in the Alerting UI.
The components used also use
useUrlParams
, which means they won't work for editing because they get data about the alert from the URL. Make it so we don't have to use this in the Alerting UI.The text was updated successfully, but these errors were encountered: