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

[Security Solution][Detections] Experiments with Alerting Event Log for Rule Monitoring #93811

Conversation

banderror
Copy link
Contributor

Ticket: #91265

Summary

Summarize your PR. If it involves visual changes include a screenshot or gif.

Checklist

Delete any items that are not applicable to this PR.

For maintainers

@banderror banderror added Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc. labels Mar 5, 2021
@banderror banderror self-assigned this Mar 5, 2021
@banderror banderror force-pushed the optimize-rule-fetching-endpoints-v2 branch from 46ddf79 to bb6181b Compare March 9, 2021 10:46
@banderror banderror force-pushed the optimize-rule-fetching-endpoints-v2 branch from bb6181b to 97d85b8 Compare March 9, 2021 12:42
@kibanamachine
Copy link
Contributor

kibanamachine commented Mar 9, 2021

⏳ Build in-progress, with failures

Failed CI Steps

History

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

cc @banderror

@banderror banderror closed this Mar 9, 2021
@banderror
Copy link
Contributor Author

See #94143

@banderror banderror deleted the optimize-rule-fetching-endpoints-v2 branch March 9, 2021 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Detections and Resp Security Detection Response Team Team: SecuritySolution Security Solutions Team working on SIEM, Endpoint, Timeline, Resolver, etc.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants