You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Fluent Bit version 2.0.5 running as a daemon set in Kubernetes clusters. The K8s env I am having at my organisation are K8s clusters at edge and around 100 clusters are there. I am getting the issue with the Fluent-Bit forwarding the logs to NewRelic, for few of the clusters that the FluentBit pod got stuck in connection timeout and not able to get any logs beyond that.
When checked we are getting the FluentBit uptime metrices which is being scrapped through prometheus. Since FluentBit image is a distroless one so even Liveness Probe can't be set to restart the pod in case if we are not getting the metric.
Connection timeout I can understand could be a network issue but pod getting stuck to timed out and not restarting or dropping the connection is an issue. Also I have checked the PR #3192 which says the issue of connection timeout is fixed in v1.7.0 and ownwards but still issue persists.
Please suggest any resolution for the same.
The text was updated successfully, but these errors were encountered:
Hi All,
I am using Fluent Bit version 2.0.5 running as a daemon set in Kubernetes clusters. The K8s env I am having at my organisation are K8s clusters at edge and around 100 clusters are there. I am getting the issue with the Fluent-Bit forwarding the logs to NewRelic, for few of the clusters that the FluentBit pod got stuck in connection timeout and not able to get any logs beyond that.
When checked we are getting the FluentBit uptime metrices which is being scrapped through prometheus. Since FluentBit image is a distroless one so even Liveness Probe can't be set to restart the pod in case if we are not getting the metric.
Connection timeout I can understand could be a network issue but pod getting stuck to timed out and not restarting or dropping the connection is an issue. Also I have checked the PR #3192 which says the issue of connection timeout is fixed in v1.7.0 and ownwards but still issue persists.
Please suggest any resolution for the same.
The text was updated successfully, but these errors were encountered: