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

Document requirements for developing a generic action type #67864

Closed
mikecote opened this issue Jun 1, 2020 · 1 comment · Fixed by #69164
Closed

Document requirements for developing a generic action type #67864

mikecote opened this issue Jun 1, 2020 · 1 comment · Fixed by #69164
Assignees
@pmuellr
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@mikecote
Copy link
Contributor

mikecote commented Jun 1, 2020

There is missing guidelines for other teams to develop generic action types. We should update the README for now (until we move to asciidoc) to have a list of requirements that is necessary for an action type to be generic.

Things like asciidoc documentation, tests, integrations with the connectors list, usability by a generic alert, license discussion, etc.
@mikecote mikecote added Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Jun 1, 2020
@elasticmachine
Copy link
Contributor

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

@mikecote mikecote mentioned this issue Jun 2, 2020
Open
59 tasks
@pmuellr pmuellr self-assigned this Jun 10, 2020
@pmuellr pmuellr mentioned this issue Jun 15, 2020
Merged
2 tasks
pmuellr added a commit to pmuellr/kibana that referenced this issue Jun 30, 2020
@pmuellr
[Alerting] document requirements for developing new action types
e9d5eab 
resolves elastic#67864

Adding this to the actions README.md, it should be published as asciidocs at GA.
pmuellr added a commit that referenced this issue Jul 3, 2020
@pmuellr
[Alerting] document requirements for developing new action types (#69164
5226ea2 
)

* [Alerting] document requirements for developing new action types

resolves #67864

Adding this to the actions README.md, it should be published as asciidocs at GA.
pmuellr added a commit to pmuellr/kibana that referenced this issue Jul 3, 2020
@pmuellr
[Alerting] document requirements for developing new action types (ela…
8951a8b 
…stic#69164)

* [Alerting] document requirements for developing new action types

resolves elastic#67864

Adding this to the actions README.md, it should be published as asciidocs at GA.
pmuellr added a commit that referenced this issue Jul 3, 2020
@pmuellr
[Alerting] document requirements for developing new action types (#69164
654ad96 
) (#70684)

* [Alerting] document requirements for developing new action types

resolves #67864

Adding this to the actions README.md, it should be published as asciidocs at GA.
@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

@pmuellr pmuellr

Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Alerting] document requirements for developing new action types pmuellr/kibana
4 participants
@pmuellr @kobelb @mikecote @elasticmachine