-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Allow multiple configurations for a sidecar #5706
Comments
Please refer to this community thread for a workaround: |
One possible way to support this, is that we add a tags list back into the your configuration could render sections based on tags.
|
Hello, |
Yeah, it would be nice to have this in the future but please focus on supporting ES 7 |
The help for the most recent Graylog version implies, that the conditional configuration of sidecars should work: I tried this but never succeeded. Seems that the if statement is somehow processed, but the tags in sidcar.yaml do not "reach" graylog when the configuration is rendered. Is this a documentation issue or a bug? Reading this issue I would say it's not correctly documented. As this feature makes a lot of sense a +1 for me to re-implement it. |
@mpibpc-mroose which version of graylog and sidecar are you using? |
both in the newest versions: Graylog: 5.0.2 Discussed that in the graylog forum, too: https://community.graylog.org/t/use-sidecar-tags-in-filebeat-config/27251 |
You need at least sidecar 1.3.0 for this. |
Hi everyone, I think we can close this now. With Graylog 5.0 (and Sidecar 1.3) we released the possibility to automatically assign Sidecar configurations, based on tags. A list of tags can be assigned in a Sidecar's YAML configuration. Collector configuration matching any of these tags will then automatically be applied to the Sidecar. Details:
Recently a related change was added to the Sidecar installer on Windows to accept tags at installation time, for convenience: |
Great but the doc is not clear about this. The doc about tags and sniplets is minimalist too. |
@BenoitPoulet which docs are you referring to specifically? |
@BenoitPoulet ah, thanks. I'll get that fixed. |
In Graylog 2, tags were a very convenient method for classifying and combining configurations for specific sidecars. E.g. a generic 'linux' tag for gathering generic logs from all Linux machines, and more specific tags that would only apply to certain machines (including these Linux machines).
Simply defining the appropriate tags in a sidecar configuration file on a server would cause it to collect the correct logs from this server, using the combined configurations for all these tags.
With the removal of tag-based configuration it looks like it is no longer possible to apply multiple configurations to a sidecar. I need to create a configuration for every single combination of (former) tags I want to use on all my servers, and combine the desired log inputs inside all these configurations using variables if I want to avoid duplication. The number of combinations can grow exponentially when more log inputs are introduced.
How difficult would it be to allow multiple configurations to be applied to a sidecar, effectively allowing the combination of different configurations without having to create a lot of compound configurations every time a new log input is introduced?
The text was updated successfully, but these errors were encountered: