elastic / kibana

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

Using OpsGenie Connector as Default Connector in Synthetics Alerting does not work #168681

Open simioa opened 9 months ago

simioa commented 9 months ago

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:

action execution failure: .opsgenie:myConnectorID: myConnectorName - error validating action params: [subAction]: expected value of type [string] but got [undefined]

Steps to reproduce:

  1. Navigate to Synthetics --> Settings
  2. On the "Alerting" Tab, create a new OpsGenie Connector by clicking on "Add connector" or select an existing one from the "Default connectors" Dropdown Menu
  3. Create a new failing Monitor. In my case I created a HTTP Ping Monitor that checks Kibana and used a wrong return code.
  4. Wait for the Monitor to go "Down"
  5. Navigate to "Stack Management" --> Rules
  6. Select "Synthetics internal alert"
  7. Click on the "History" Tab and look for the Entry with the Errored Action. The Log will look like the Error-Message from above

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

elasticmachine commented 9 months ago

Pinging @elastic/uptime (Team:uptime)

elasticmachine commented 6 months ago

Pinging @elastic/obs-ux-infra_services-team (Team:obs-ux-infra_services)

jennypavlova commented 3 weeks ago

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:

nedkoh commented 2 weeks ago

When can we expect this to be fixed? Can we use the OpsGenie webhook connector as a workaround for the time-being?

elasticmachine commented 1 week ago

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)