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
Description
The metrics for the log buffer are based on a custom sidecar tracking the underlying filesystem. That sidecar is not correlating the buffer instance with an actual logpipeline. With that, the flow health status of LogPipeline A can get negative if the buffer of LogPipeline B is running full. Also, a leftover buffer of a previous pipeline can stimulate this.
Criterias
The flow status of a pipeline should be isolated on the pipeline itself by looking only at the metrics of the dedicated buffer
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.
This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.
Description
The metrics for the log buffer are based on a custom sidecar tracking the underlying filesystem. That sidecar is not correlating the buffer instance with an actual logpipeline. With that, the flow health status of LogPipeline A can get negative if the buffer of LogPipeline B is running full. Also, a leftover buffer of a previous pipeline can stimulate this.
Criterias
The text was updated successfully, but these errors were encountered: