-
Notifications
You must be signed in to change notification settings - Fork 253
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
Add gelf output plugin to fluentbit #882
Add gelf output plugin to fluentbit #882
Conversation
4327a36
to
6e21891
Compare
Signed-off-by: alexandre.vilain <[email protected]>
6e21891
to
a380287
Compare
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.
Hi @wenchajun ! Thanks for the review.
I don't think it's missing because it's handled by this part of the code: https://github.com/fluent/fluent-operator/blob/master/apis/fluentbit/v1alpha2/clusteroutput_types.go#L153 If I create the following manifest: apiVersion: fluentbit.fluent.io/v1alpha2
kind: ClusterOutput
metadata:
name: test
labels:
fluentbit.fluent.io/enabled: "true"
fluentbit.fluent.io/mode: "fluentbit-only"
spec:
matchRegex: "*"
gelf:
host: 127.0.0.1
port: 12202
mode: tls
tls:
verify: true The generated configuration looks like: [Output]
Name gelf
Match_Regex *
Host gra1.logs.ovh.com
Port 12202
Mode tls
tls On
tls.verify true Here it uses matchRegex but it's the same as for match. I think that it's an error on the GELF output documentation as the "Match" field is part of every output plugin. |
@patrick-stephens @wanjunlei what do you think? |
Not sure what you're querying here - all filter+output plugins support |
Agree, Match & MatchRegex are common attributes of output plugins: |
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #881
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: