[Bug]: Syslog health monitor sends sidecar data before it is ready

[lalitadithya]

Prerequisites

• I searched existing issues
• I can reproduce this issue

Bug Description

In some cases, the sidecar container takes longer than expected to become ready and in such cases the syslog health monitor will try sending it data and will eventually drop the message. This is rare but it does cause the possibility of missing some XIDs in some cases.

Explore if using https://kubernetes.io/docs/concepts/workloads/pods/sidecar-containers/ would help here

Component

Health Monitor

Steps to Reproduce

1. Slow down the startup of the sidecar container
2. Notice that the syslog health monitor logs for errors and see that it eventually will drop the message

Environment

• NVSentinel version: all
• Kubernetes version: v1.30
• Deployment method: ArgoCD

Logs/Output

No response