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

Webhook Alert doesn't retain added HTTP header settings #70907

Closed
TheRiffRafi opened this issue Jul 7, 2020 · 2 comments · Fixed by #71924
Closed

Webhook Alert doesn't retain added HTTP header settings #70907

TheRiffRafi opened this issue Jul 7, 2020 · 2 comments · Fixed by #71924
Assignees
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@TheRiffRafi
Copy link

Kibana version:
7.8.0
Elasticsearch version:
7.8.0
Server OS version:
Cloud ESS
Browser version:
Any Browser
Browser OS version:
Any OS

Describe the bug:
Added HTTP header to Webhook connector is not persisted after saving the webhook connector.

Steps to reproduce:
1.Kibana > Stack Management > Alerts and Actions > Connectors > Create Webhook Connector > Add HTTP Header > Save
2. Edit newly created connector > Added HTTP Header not listed.

Expected behavior:
Editing the connector should show the added HTTP headers.

Errors in browser console (if relevant):
None

Any additional context:
I've been unable to check if the header is persisted somewhere else, but this is because I don't know where to look.

@TheRiffRafi TheRiffRafi changed the title Webhook Alert doesn't retain header settings Webhook Alert doesn't retain added HTTP header settings Jul 7, 2020
@pmuellr
Copy link
Member

pmuellr commented Jul 15, 2020

I'm able to repro this - it does appear to be saved with the action, just not displayed again when the action is edited again.

I verified that by listing the actions with a curl invocation:

$ curl https://user:password@kibana-host-name:port/api/actions
[
  {
    "id": "8e855aae-2dbe-473a-85b2-5ea9c5c32a84",
    "actionTypeId": ".webhook",
    "name": "sample webhook",
    "config": {
      "method": "post",
      "url": "http://example.com",
      "headers": {
        "foo": "bar"
      }
    },
    "isPreconfigured": false,
    "referencedByCount": 0
  },
  ...
]

The header I added was foo: bar, which did get saved with the action, but was not displayed when I edited the action again.

@pmuellr pmuellr added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jul 15, 2020
@elasticmachine
Copy link
Contributor

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

@YulNaumenko YulNaumenko self-assigned this Jul 15, 2020
@kobelb kobelb added the needs-team Issues missing a team label label Jan 31, 2022
@botelastic botelastic bot removed the needs-team Issues missing a team label label Jan 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants