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

[actions] create a generic webhook endpoint for testing actions #86233

Closed
pmuellr opened this issue Dec 17, 2020 · 4 comments
Closed

[actions] create a generic webhook endpoint for testing actions #86233

pmuellr opened this issue Dec 17, 2020 · 4 comments
Labels
discuss estimate:needs-research Estimated as too large and requires research to break down into workable issues estimate:small Small Estimated Level of Effort Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) test-coverage issues & PRs for improving code test coverage

Comments

@pmuellr
Copy link
Member

pmuellr commented Dec 17, 2020

While trying to diagnose a problem with a customer using an action, I happened upon https://pipedream.com , which is a service which allows you to create "webhook" endpoints on their server, and then be able to see the incoming requests to the webhook.

A capability like this could be useful in Kibana itself. To help diagnose action issues, customers could point to an endpoint we provide in Kibana specifically to test http actions tied to specific URLs, by using this "test" interface instead.

I haven't looked too deeply into pipedream. I'm not sure that providing absolutely correct HTTP responses for any service would be required, for diagnostic purposes, it's seems like usually we just want to see what the request ends up looking like on the server. So it could always return a 404 response, or such.

But we'd want to capture the requests so that you could then see what requests had been made, after the fact. And then have some UI for it, etc, etc.

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

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

@zez3
Copy link

zez3 commented Mar 12, 2021

One could complicate things with webhooks triggering specific actions or Elastic could implement a more generic JSON-RPC Connector that stores session based tokens for reuse

@gmmorris gmmorris added the loe:medium Medium Level of Effort label Jul 14, 2021
@gmmorris gmmorris added test-coverage issues & PRs for improving code test coverage loe:needs-research This issue requires some research before it can be worked on or estimated estimate:small Small Estimated Level of Effort estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Aug 16, 2021
@gmmorris gmmorris removed loe:needs-research This issue requires some research before it can be worked on or estimated loe:medium Medium Level of Effort labels Sep 2, 2021
@ymao1
Copy link
Contributor

ymao1 commented Nov 19, 2021

Closing due to lack of activity

@ymao1 ymao1 closed this as completed Nov 19, 2021
@zez3
Copy link

zez3 commented Nov 19, 2021

Unfortunately I don't have any news when Fortinet is going to implement a standard API

@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
discuss estimate:needs-research Estimated as too large and requires research to break down into workable issues estimate:small Small Estimated Level of Effort Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) test-coverage issues & PRs for improving code test coverage
Projects
None yet
Development

No branches or pull requests

7 participants