Skip to content
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

output: Show better message for different secondary type #2751

Merged
merged 1 commit into from
Jan 7, 2020

Conversation

repeatedly
Copy link
Member

Signed-off-by: Masahiro Nakagawa repeatedly@gmail.com

Which issue(s) this PR fixes:
No issue in this repository.

What this PR does / why we need it:
Current message is bit misleading for users. Some output plugins work with primary.

Docs Changes:
No need for now.

Release Note:
Same as title.

Signed-off-by: Masahiro Nakagawa <repeatedly@gmail.com>
@@ -387,7 +387,7 @@ def configure(conf)
@secondary.acts_as_secondary(self)
@secondary.configure(secondary_conf)
if (self.class != @secondary.class) && (@custom_format || @secondary.implement?(:custom_format))
log.warn "secondary type should be same with primary one", primary: self.class.to_s, secondary: @secondary.class.to_s
log.warn "Use different plugin for secondary. Check the plugin works with primary like secondary_file", primary: self.class.to_s, secondary: @secondary.class.to_s
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have two questions.

  • Why this warning is needed? if it won't work, I think it should be error.
  • How to check this? > Check the plugin works with primary like secondary_file

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this warning is needed? if it won't work, I think it should be error.
How to check this? > Check the plugin works with primary like secondary_file

Hard to reject the plugin by fluentd side because it depends on implementation issue.
If users can't judge the plugin works as secondary, users should use primary plugin or secondary_file.

@repeatedly repeatedly merged commit 4d44ad8 into master Jan 7, 2020
@repeatedly repeatedly deleted the better-log-for-different-secondary branch January 7, 2020 05:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature request or improve operations
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants