Deprecate SQS queue global setting - #10672
Merged
chemamartinez merged 6 commits intoAug 6, 2024
Merged
Conversation
chemamartinez
added
Integration:carbon_black_cloud
chemamartinez
marked this pull request as ready for review
July 31, 2024 19:27
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
efd6
reviewed
Aug 1, 2024
💚 Build Succeeded
History
|
|
efd6
approved these changes
Aug 5, 2024
|
Package carbon_black_cloud - 2.4.0 containing this change is available at https://epr.elastic.co/search?package=carbon_black_cloud |
|
Package cloudflare_logpush - 1.22.0 containing this change is available at https://epr.elastic.co/search?package=cloudflare_logpush |
|
Package jamf_protect - 2.3.0 containing this change is available at https://epr.elastic.co/search?package=jamf_protect |
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 4, 2025
Recent tests and reports have revealed that using the same SQS queue for multiple data streams results in data loss even with a very low event load. For this reason, this pull request updates the affected integrations by forcing users to configure a separate SQS queue for each enabled data stream, as well as updating the related documentation for their knowledge.
harnish-crest-data
pushed a commit
to chavdaharnish/integrations
that referenced
this pull request
Feb 5, 2025
Recent tests and reports have revealed that using the same SQS queue for multiple data streams results in data loss even with a very low event load. For this reason, this pull request updates the affected integrations by forcing users to configure a separate SQS queue for each enabled data stream, as well as updating the related documentation for their knowledge.
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
3 participants
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.
Proposed commit message
Recent tests and reports have revealed that using the same SQS queue for multiple data streams results in data loss even with a very low event load.
For this reason, this pull request updates the affected integrations by forcing users to configure a separate SQS queue for each enabled data stream, as well as updating the related documentation for their knowledge.
Checklist
changelog.ymlfile.Related issues