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.

Sign up for GitHub

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

Jump to bottom

VictorOps action type #56404

Open
peterschretlen opened this issue Jan 30, 2020 · 2 comments
Open

VictorOps action type #56404

peterschretlen opened this issue Jan 30, 2020 · 2 comments
Labels
connectivity Issues relating to connectivity between Kibana and external services enhancement New value added to drive a business result estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@peterschretlen
Copy link
Contributor

Describe the feature:

Send alerts and incident details into VictorOps using their REST API.

Like other action types, the key property when binding to an alert will be message (the state_message property), but this action should be similar to PagerDuty in expressiveness, including as many JSON body fields as practical.
@peterschretlen peterschretlen added Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jan 30, 2020
@elasticmachine
Copy link
Contributor

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

@clintongormley clintongormley mentioned this issue Jan 30, 2020
Open
27 tasks
@mikecote mikecote added this to Mid Term in Make it Action Feb 4, 2020
@mikecote mikecote moved this from Mid Term to 7.x - Tentative in Make it Action Aug 6, 2020
@mikecote mikecote removed this from 7.x - Candidates in Make it Action Jan 27, 2021
@mikecote mikecote added this to 8.x - Candidates in Kibana Alerting Jan 27, 2021
@mikecote mikecote moved this from 8.x - Candidates to 7.x - Candidates in Kibana Alerting Jan 27, 2021
@mikecote
Copy link
Contributor

mikecote commented Feb 4, 2021

Moving from 7.x - Candidates to 8.x - Candidates (Backlog) after the latest 7.x planning session.

@mikecote mikecote moved this from 7.x - Candidates to 8.x - Candidates in Kibana Alerting Feb 4, 2021
@gmmorris gmmorris added the Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework label Jul 1, 2021
@gmmorris gmmorris added the loe:needs-research This issue requires some research before it can be worked on or estimated label Jul 14, 2021
@gmmorris gmmorris added enhancement New value added to drive a business result connectivity Issues relating to connectivity between Kibana and external services estimate:needs-research Estimated as too large and requires research to break down into workable issues labels Aug 13, 2021
@gmmorris gmmorris removed the loe:needs-research This issue requires some research before it can be worked on or estimated label Sep 2, 2021
@mikecote mikecote removed this from Backlog in Kibana Alerting Jan 6, 2022
@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
Assignees
No one assigned
Labels
connectivity Issues relating to connectivity between Kibana and external services enhancement New value added to drive a business result estimate:needs-research Estimated as too large and requires research to break down into workable issues Feature:Actions/ConnectorTypes Issues related to specific Connector Types on the Actions Framework Feature:Actions Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
No open projects
AppEx: ResponseOps - Execution & Connectors
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
5 participants
@gmmorris @kobelb @mikecote @peterschretlen @elasticmachine