Open simioa opened 9 months ago
Pinging @elastic/uptime (Team:uptime)
Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)
After discussing with @shahzad31 I want to add some details here:
Ops-genie connector has UptimeConnectorFeatureId
(https://github.com/elastic/kibana/blob/main/x-pack/plugins/stack_connectors/server/connector_types/opsgenie/index.ts#L35) in supported features but it's not part of the populated alerts actions (https://github.com/elastic/kibana/blob/main/x-pack/plugins/observability_solution/synthetics/common/rules/alert_actions.ts#L42)
To fix this issue we have 2 options:
ALLOWED_ACTION_TYPES
(For reference https://github.com/elastic/kibana/pull/136331). When can we expect this to be fixed? Can we use the OpsGenie webhook connector as a workaround for the time-being?
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)
Kibana version: 8.9.1 Elasticsearch version: 8.9.1 Original install method (e.g. download page, yum, from source, etc.): docker
Describe the bug: I tried setting up an OpsGenie Default Connector in Synthetics but was unable to get it to work. I was able to select the OpsGenie Connector in the Drop-Down Menu, but when I simulated a failing Monitor, no Alert was generated. I then navigated to the Rule History to look for the Issue und saw the following Error-Message:
Steps to reproduce:
Expected behavior: The alert should be successfully created in OpsGenie
Provide logs and/or server output (if relevant): Server Output is the same as the Error-Message above