-
Notifications
You must be signed in to change notification settings - Fork 183
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: set source name and category in the FluentD output for events #2222
Conversation
I'll update the changelog after we release 2.7. In the meantime, this is ready for review. |
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.
This pull request contains invalid labels. Please remove all of the following labels: ['do-not-merge/hold']
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.
Please add a changelog entry
2cfedf7
to
2c55fda
Compare
We've been setting it directly on the source in the setup Terraform manifest. Instead, do it in the output plugin and make it configurable. This makes it both easier to test and makes it work correctly if setup is disabled.
2c55fda
to
f246ce3
Compare
A bug was introduced in v2.8.0 (#2222) that made the `fluentd.events.sourceCategory` non-functional.
A bug was introduced in v2.8.0 (#2222) that made the `fluentd.events.sourceCategory` non-functional.
A bug was introduced in v2.8.0 (#2222) that made the `fluentd.events.sourceCategory` non-functional.
Description
We've been setting source name and category directly on the source in the setup Terraform manifest. Instead, do it in the output plugin and make it configurable.
This makes it both easier to test and makes it work correctly if setup is disabled.
Also add a basic integration test for events.
Checklist
Testing performed