Replies: 1 comment 1 reply
-
|
I know I could remove the fluent-bit service and then re-define it with new startup cmd, but we consider it as plan B and prefer to modify the service before or during installation if anyone has related experience. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
You're right, we should transition the config file to YAML by default @cosmo0920 . Lines 1324 to 1340 in 8994bfc |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello Everyone,
The background is that we use chocolatey tools to re-pack fluent-bit MSI binary and generate one nupkg file with customized configuration in it.
After a buck provisioning, all windows servers (500+) will be installed fluent-bit, then all of them will start to collect local windows event/software logs and sent logs to one bastion host without any interventions.
From Oct, we used v3.1.9 with classic mode conf files and it almost finished our requirements. However, as v3.2.1 identified, classic mode will be deprecated at end of 2025, so we change to use v3.2.1 from now.
BTW, for v3.2.1, the default installed configuration file still use .conf of classic mode. We deleted all of them and replaced with new .yaml ones.
In short, my question is that with fluent-bit.yaml, how to change the startup service command for MSI installed case
from "$PATH\fluent-bit.exe -c $PATH\fluent-bit.conf"
to "$PATH\fluent-bit.exe -c $PATH\fluent-bit.yaml"
after fluent-bit MSI installed.
I ever find INSTALL_ROOT parameter from MSI log file to re-located the installation path, but for above change, still have no idea of which parameter would work for me.
Appreciate for any help on this.
Beta Was this translation helpful? Give feedback.
All reactions