-
Notifications
You must be signed in to change notification settings - Fork 466
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
Deprecate SQS queue global setting #10672
Deprecate SQS queue global setting #10672
Conversation
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
💚 Build Succeeded
History
|
Quality Gate passedIssues Measures |
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 |
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.
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.yml
file.Related issues