-
Notifications
You must be signed in to change notification settings - Fork 444
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
[Carbon Black Cloud] - Introduced data stream specific SQS queues #9303
Conversation
…tation for making integration GA
…S queues, updated docs accordingly
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nit. Rest LGTM 👍🏼
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
cc @ShourieG |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
Package carbon_black_cloud - 1.21.0 containing this change is available at https://epr.elastic.co/search?package=carbon_black_cloud |
Package carbon_black_cloud - 1.21.0 containing this change is available at https://epr.elastic.co/search?package=carbon_black_cloud |
Type of change
Proposed commit message
Introduced data stream specific SQS queues to address the issue of data loss while using a single SQS queue for all data streams and then filtering out data using file selectors. The filtering using file selectors in a particular data stream caused the data for other data streams to get dropped by the SQS queue as described in this issue: #9289. This PR introduces an optional SQS queue per data stream while still keeping support for the original global SQS queue. The data stream specific queues will always override the global queues. The default file selector regexes have been commented out. This approach was adopted instead of just outright removing the older queues and file selectors was to maintain compatibility with the previous versions and not cause a breaking change. The updated setup instructions and update warnings have been documented to make the end user aware of the new functionality.
Checklist
changelog.yml
file.Author's Checklist
How to test this PR locally
Related issues
Test Results
Screenshots