search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.64k stars 8.22k forks source link

[Synthetics UI] Support disabling a single monitor location #136111

Open dominiqueclarke opened 2 years ago

dominiqueclarke commented 2 years ago

As a Synthetics user, I'd like to be able to disable monitor runs from a specific location.

Individual locations can be disabled from the monitor grid item actions and the monitor details flyout.

Screen Shot 2022-07-11 at 10 01 37 AM Screen Shot 2022-07-11 at 9 59 50 AM

We currently do not have not have a workflow that supports disabling a single monitor location, other than removing that monitor location from from the configuration entirely. Removing the monitor location from the configuration entirely is not desired, as disabled locations should still be able to be visualized from the monitor overview grid. To support this, we'll need to keep locations selected on the monitor configuration, while marking it as disabled when sending to the location's service url.

Outstanding questions

Interaction with the management page

The management page allows for enabling/disabling the overall monitor, essentially all monitor locations. For this reason, we'll need to think about how that impacts overwriting enablement/disablement of individual locations. For example, if a specific location was disabled, then the user toggled the monitor to disabled on this page, then back to enabled, does that renable all locations? Will any actions taken here always overwrite all locations? Also, do we need to visualize which locations are disabled/enabled here in some way?

Impact to the add/edit page

Do we need to support enabling or disabling of individual locations from the add/edit page, or visualize if specific locations are currently enabled or disabled?

elasticmachine commented 2 years ago

Pinging @elastic/uptime (Team:uptime)

hbharding commented 2 years ago

@dominiqueclarke I'm not sure if we need the ability to disable monitors per location, and we can probably close this issue. I think my earlier designs may have made this look possible. While there might be a use case for this, I think we get by without this behavior for the initial release.

I think removing the option to disable a monitor from the monitor card / overview page might make this less confusing. image