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

Prepare alerts and actions for feature controls #52956

Merged
merged 7 commits into from
Dec 18, 2019

Conversation

mikecote
Copy link
Contributor

@mikecote mikecote commented Dec 12, 2019

Resolves #51120

In this PR, I'm adding to the alerts a consumer field that will represent the owning application of the alert. We will be able to use this to apply feature controls once it arrives.

This seems to be the only extra piece of information we need at this time to satisfy feature controls down the line.

@mikecote mikecote added Feature:Alerting v8.0.0 release_note:skip Skip the PR/issue when compiling release notes v7.6.0 Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) labels Dec 12, 2019
@mikecote mikecote self-assigned this Dec 12, 2019
@mikecote mikecote force-pushed the alerting/save-consumer-producer branch from ac2938c to 510bf70 Compare December 13, 2019 21:20
@mikecote
Copy link
Contributor Author

@elasticmachine merge upstream

@mikecote mikecote marked this pull request as ready for review December 13, 2019 21:28
@mikecote
Copy link
Contributor Author

@elasticmachine merge upstream

@mikecote mikecote requested a review from a team December 17, 2019 14:03
Copy link
Member

@pmuellr pmuellr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mikecote
Copy link
Contributor Author

@elasticmachine merge upstream

@mikecote
Copy link
Contributor Author

mikecote commented Dec 18, 2019

cc @elastic/siem and @elastic/stack-monitoring about upcoming breaking change. New consumer field will be required when calling the create alert API, this is used to link an alert to your application which we'll use for feature controls down the line.

Copy link
Contributor

@gmmorris gmmorris left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but you have a merge conflict 😬

@@ -174,6 +174,7 @@ export const getResult = (): RuleAlertType => ({
name: 'Detect Root/Admin Users',
tags: [`${INTERNAL_RULE_ID_KEY}:rule-1`],
alertTypeId: 'siem.signals',
consumer: 'siem',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice! 👍

Copy link
Contributor

@FrankHassanabad FrankHassanabad left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thank you for updating our code on our side for us.

@elasticmachine
Copy link
Contributor

💚 Build Succeeded

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

@mikecote mikecote merged commit 4069c4a into elastic:master Dec 18, 2019
mikecote added a commit to mikecote/kibana that referenced this pull request Dec 18, 2019
* Save consumer with alert

* Make consumer mandatory
mikecote added a commit that referenced this pull request Dec 19, 2019
* Save consumer with alert

* Make consumer mandatory
@mikecote
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Alerting release_note:skip Skip the PR/issue when compiling release notes review Team:ResponseOps Label for the ResponseOps team (formerly the Cases and Alerting teams) v7.6.0 v8.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Preparation alerts and actions for feature controls
5 participants