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.

Sign up for GitHub

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

Jump to bottom

Plugin macros #19

Closed
jvassev opened this issue Jul 5, 2018 · 1 comment
Closed

Plugin macros #19

jvassev opened this issue Jul 5, 2018 · 1 comment
Labels
enhancement New feature or request

Comments

@jvassev
Copy link
Contributor

jvassev commented Jul 5, 2018

Following the discussion in #17 a macro for output plugins is needed. Consider this example:
kube-system.conf:

kube-system.conf
<plugin default_output>
  @type es
  username admin
  password s3cret
  buffer_size 1m
</plugin>

demo.conf:
<match **>
  @type default_output
  buffer_size 5m
</match>

When processing the config for the demo namespace, the @type default_output should be replaced with the definition of the plugin in the kube-system namespace:

demo.conf (after processing):
<match **>
  @type es
  username admin
  password s3cret
  buffer_size=5m
</match>

All params defined at the call site override the parameters in the plugin definition. Also, all post-processing rules should be applied: .pos file path rewriting, tag validation, etc.
@jvassev jvassev added the enhancement New feature or request label Jul 5, 2018
jvassev added a commit that referenced this issue Jul 6, 2018
@jvassev
Virtual plugins (#19)
025d688 
The non-standard directive <plugin> define a plugin when used in the
kube-system namspace.

Other neamespaces can refer to this plugin definition and use it,
optionally overriding some params.

Virtual plugins help admin define "default" outputs once and namespaces
owners don't need details about where the logs go (concret output
plugin) neither how (any passwords, urls related to the sink
configuration).
@jvassev jvassev mentioned this issue Jul 6, 2018
Closed
@jvassev
Copy link
Contributor Author

jvassev commented Jul 23, 2018

This feature is scheduled for release in 1.6.0. Closing the issue.

@jvassev jvassev closed this as completed Jul 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jvassev