[Carbon Black Cloud] - Introduced data stream specific SQS queues - #9303
Merged
Conversation
…tation for making integration GA
…S queues, updated docs accordingly
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
kcreddy
approved these changes
Mar 7, 2024
🚀 Benchmarks reportTo see the full report comment with |
�� Build Succeeded
cc @ShourieG |
|
|
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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


0.0% Duplication on New Code
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.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Test Results
Screenshots