[Alerting] Edit alert created on UPTIME UI

[enotspe]

It would be nice to be able to edit an alert that has been created from UPTIME UI. Furthermore, on alerted instances, it will be nice to see wich monitor.ids triggered the alert

[elasticmachine]

Pinging @elastic/kibana-alerting-services (Team:Alerting Services)

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[mikecote]

@elastic/uptime let us know if you need help with anything. I believe we've discussed this before but requiresAppContext is set to true here

kibana/x-pack/plugins/uptime/public/lib/alert_types/monitor_status.tsx

Line 74 in b15578c

requiresAppContext: true,

which prevents these alert types from being editable.

[justinkambic]

@mikecote thanks - we're actually working on this right now, our changes will likely resolve this issue. The main challenge is our alert UI elements rely on some state that's only available today if our app mounts, we're hoping to make these services available at start time instead, which would make us ok to set requiresAppContext to false.

[shahzad31]

@enotspe

Furthermore, on alerted instances, it will be nice to see wich monitor.ids triggered the alert

By this you means in the actual alert message monitor.id should be included? i think this should be possible even right now. What alert message are you getting right now? and how do you think it should be formatted?

[enotspe]

No. I mean when you enter alert details, i see xpack.uptime.alert..... which does not give any info. I think we should be seeing all the monitor.ids that are down.

According to the documentation, these are called alert instances

https://user-images.githubusercontent.com/47488630/82771481-d988d280-9e01-11ea-9839-76074f0c75e5.png

[andrewvc]

Closing in favor of elastic/uptime#179