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

[Actions] Implement number of active connectors by action type #60046

Closed
YulNaumenko opened this issue Mar 12, 2020 · 2 comments
Closed

[Actions] Implement number of active connectors by action type #60046

YulNaumenko opened this issue Mar 12, 2020 · 2 comments
Labels
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)

Comments

@YulNaumenko
Copy link
Contributor

This is added as a separate issue and was not included into PR #58081, because of the complexity of retrieving and binding actionTypeId with relations connector id (should be unique across the related alerts). Probably should be considered to extend alert.actions with connector id or some other way of getting and aggregating data.
@mikecote
Copy link
Contributor

It was discussed to use a meta issue for now, moving to #60315.

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

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

@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
Feature:Alerting Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kobelb @mikecote @elasticmachine @YulNaumenko