-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Handle authorization errors in Kafka output #42401
Handle authorization errors in Kafka output #42401
Conversation
b11da27
to
a5fe2e6
Compare
This pull request is now in conflicts. Could you fix it? 🙏
|
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
|
When there is an authorisation error in the Kafka output, the events are dropped and an error message is logged.
a5fe2e6
to
d1e1755
Compare
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
When there is an authorisation error in the Kafka output, the events are dropped and an error message is logged. (cherry picked from commit 5720300)
When there is an authorisation error in the Kafka output, the events are dropped and an error message is logged. (cherry picked from commit 5720300) Co-authored-by: Tiago Queiroz <[email protected]>
Proposed commit message
When there is an authorisation error in the Kafka output, the events are dropped and an error message is logged.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.## Disruptive User Impact## Author's ChecklistHow to test this PR locally
Run the tests added by this PR:
If you want to run any Beat yourself, you can modify the test so it only starts the mock and waits, then configure a Beat to connect to it.
Related issues
## Use cases## Screenshots## Logs