Closed jacekmackiewicz closed 4 years ago
.\fluent-bit.exe -h doesn't show gelf in Outputs :(
.\fluent-bit.exe -h doesn't show gelf in Outputs :(
@jacekmackiewicz This is because we have not ported out_gelf
to Windows yet.
I'm currently looking at the code, and it seems that we need to clean up a few things to get it compilable on Windows...
Ok, in the meantime I'm looking into http output and it seems to be working fine. Just not sure yet if it's a good workaround.
[OUTPUT] Name http Match * Host
Port 12201 URI /gelf Format gelf Gelf_host_key stream Gelf_short_message_key log
Ok, in the meantime I'm looking into http output and it seems to be working fine. Just not sure yet if it's a good workaround.
@jacekmackiewicz It is OK. the HTTP plugin also supports Graylog format.
out_gelf
has some additional feature (like sending packets via UDP), but
the basic functionality is same.
By the way, I am currently working on the Windows port of out_gelf
. I'll
post update here once I've finished the porting.
OK. Now the Windows port patch has been land on the main line.
You will see the GELF plugin enabled on Windows builds since the next major release.
As such, I close this issue as resolved.
Bug Report
Describe the bug Tried using gelf output on Windows but receiving 'gelf cannot be loaded'.
To Reproduce Follow instructions in docs: https://docs.fluentbit.io/manual/installation/windows Add gelf output described in docs: https://docs.fluentbit.io/manual/pipeline/outputs/gelf
Expected behavior Agent starts sending logs to Graylog gelf input.
Screenshots `Fluent Bit v1.5.6
Output plugin 'gelf' cannot be loaded Error: You must specify an output target. Aborting`
Your Environment
[INPUT] Name tail Path c:\ProgramData\Docker\containers\\-json.log Refresh_Interval 5 Ignore_Older 10s Rotate_Wait 5 DB c:\DB\logs.db
[OUTPUT] Name gelf Match * Host
Port 12201
Mode tcp
Gelf_Short_Message_Key log`