-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Windows executable missing gelf output #2547
Comments
.\fluent-bit.exe -h doesn't show gelf in Outputs :( |
@jacekmackiewicz This is because we have not ported I'm currently looking at the code, and it seems that we need to clean up a few things |
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. By the way, I am currently working on the Windows port of |
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 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
`[SERVICE]
flush 5
daemon Off
log_level info
parsers_file parsers.conf
plugins_file plugins.conf
http_server Off
http_listen 0.0.0.0
http_port 2020
storage.metrics on
[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`
The text was updated successfully, but these errors were encountered: