-
Notifications
You must be signed in to change notification settings - Fork 204
fix: updated excluded error strings #6031
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
fix: updated excluded error strings #6031
Conversation
|
This pull request does not have a backport label. Could you fix it @kaanyalti? 🙏
|
|
|
cmacknz
left a comment
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.
We should one day downgrade these errors in beats to warnings since most of them are safe to ignore.
|
* fix: updated excluded error strings * fix: added error string (cherry picked from commit cbb08c9)
* fix: updated excluded error strings * fix: added error string (cherry picked from commit cbb08c9)
* fix: updated excluded error strings * fix: added error string (cherry picked from commit cbb08c9)
* fix: updated excluded error strings * fix: added error string
* fix: updated excluded error strings * fix: added error string (cherry picked from commit cbb08c9)
* fix: updated excluded error strings * fix: added error string (cherry picked from commit cbb08c9)





What does this PR do?
Updates exlcudeded error strings in the logs_ingestion_test
Why is it important?
Error messages generated by the "add_cloud_metadata" processor have been updated as shown here. These changes break the test case that is the subject of this PR.
Checklist
[ ] I have commented my code, particularly in hard-to-understand areas[ ] I have made corresponding changes to the documentation[ ] I have made corresponding change to the default configuration files[ ] I have added tests that prove my fix is effective or that my feature works[ ] I have added an entry in(https://github.com/elastic/elastic-agent#changelog)./changelog/fragmentsusing the [changelog tool][ ] I have added an integration test or an E2E test