fluent / fluent-operator

Operate Fluent Bit and Fluentd in the Kubernetes way - Previously known as FluentBit Operator
Apache License 2.0
587 stars 250 forks source link

Fluent bit deployed with Fluent Operator doesn't work! #1122

Closed vi4vikas closed 7 months ago

vi4vikas commented 7 months ago

I have deployed a fluent-bit daemon set with the help of fluent-operator. But once the fluent bit pods are up, the only logs I can see are the CPU utilisation. A continuous stream of similar lines:

[0] cpu.local: [[1712140245.019524591, {}], {"cpu_p"=>3.000000, "user_p"=>1.375000, "system_p"=>1.625000, "cpu0.p_cpu"=>3.000000, "cpu0.p_user"=>2.000000, "cpu0.p_system"=>1.000000, "cpu1.p_cpu"=>4.000000, "cpu1.p_user"=>3.000000, "cpu1.p_system"=>1.000000, "cpu2.p_cpu"=>4.000000, "cpu2.p_user"=>2.000000, "cpu2.p_system"=>2.000000, "cpu3.p_cpu"=>4.000000, "cpu3.p_user"=>1.000000, "cpu3.p_system"=>3.000000, "cpu4.p_cpu"=>7.000000, "cpu4.p_user"=>3.000000, "cpu4.p_system"=>4.000000, "cpu5.p_cpu"=>1.000000, "cpu5.p_user"=>0.000000, "cpu5.p_system"=>1.000000, "cpu6.p_cpu"=>2.000000, "cpu6.p_user"=>1.000000, "cpu6.p_system"=>1.000000, "cpu7.p_cpu"=>0.000000, "cpu7.p_user"=>0.000000, "cpu7.p_system"=>0.000000}]

Also, I cannot see the logs being transported or I can not even see the metrics out of 2020 port as I get: curl: (7) Failed to connect to 100.xx.xx.106 port 2020 after 0 ms: Couldn't connect to server

Any help on this. I am using fluent operator v2.7.0 and fluent bit v2.2.0. Let me know if any more information is required from my side,

patrick-stephens commented 7 months ago

This sounds like you have the default config applied rather than any custom one. I would suggest raising this with the relevant info in the fluent-operator repo: https://github.com/fluent/fluent-operator

My guess is somehow your config map is not being applied but it'll depend on the specific set up you have. I would also encourage you to follow any issue templates and provide full details on your configuration and what you did.

github-actions[bot] commented 7 months ago

@vi4vikas this issue was automatically closed because it did not follow the issue template