Skip to content
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

[Stack Monitoring] Alert editing fly-out shows outdated alert parameters after editing #94440

Open
weltenwort opened this issue Mar 11, 2021 · 1 comment
Assignees
Labels
bug Fixes for quality problems that affect the customer experience Feature:Stack Monitoring Team:Monitoring Stack Monitoring team

Comments

@weltenwort
Copy link
Member

Kibana version: 7.12.0-BC4

Elasticsearch version: 7.12.0-BC4

Original install method (e.g. download page, yum, from source, etc.): cloud

Describe the bug: After editing an alert via the fly-out from the stack monitoring UI, opening the same alert editing flyout again shows the values before the last edit.

Steps to reproduce:

  1. Navigate to stack monitoring
  2. Ensure the built-in alerts are present
  3. Make a change to one of the alerts via the fly-out and save the change (such as changing the message)
  4. Open the editing fly-out for the same alert again immediately afterwards
  5. Observe, that the values don't reflect the last edit

Expected behavior: The fly-out is populated with up-to-date alert configuration parameters when it's being opened.

@weltenwort weltenwort added bug Fixes for quality problems that affect the customer experience Team:Monitoring Stack Monitoring team Feature:Stack Monitoring labels Mar 11, 2021
@elasticmachine
Copy link
Contributor

Pinging @elastic/stack-monitoring (Team:Monitoring)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Fixes for quality problems that affect the customer experience Feature:Stack Monitoring Team:Monitoring Stack Monitoring team
Projects
None yet
Development

No branches or pull requests

3 participants