topic Re: How to reduce time it takes to perform a health check on dead pod in Container platforms

How to reduce time it takes to perform a health check on dead pod?

heramb_sawant — Wed, 17 Dec 2025 12:40:32 GMT

Hi Team,
Node/host having k8s pods , later for some reason pods were killed. Though pods were not exist(already killed) , host having oneagent , was still looking for tcp connectivity with process running on that pod.

Can someone please tell me how we can minimize the time it takes to perform a health check on dead pod? currently its more than 15 min and alert remain open for long time, it is too long. I would say DT should look for the pod for one minute and if doesn’t exist don’t report.

Regards,
Heramb Sawant

Re: How to reduce time it takes to perform a health check on dead pod

heramb_sawant — Mon, 30 Sep 2024 12:50:37 GMT

Any help will be appreciated.

Re: How to reduce time it takes to perform a health check on dead pod

IzabelaRokita — Fri, 06 Jun 2025 08:59:33 GMT

Hey @heramb_sawant, did you manage to find the solution to your problem? If so, it would be amazing if you've shared it with the rest of the Community! If not, let me know, and I'll look for some further assistance 😊

Re: How to reduce time it takes to perform a health check on dead pod

Mizső — Fri, 06 Jun 2025 11:58:15 GMT

Hi @heramb_sawant,

You can play with the time at the anomaly detection section globally or namespace level. I guess non-ready pod state could be good for you.

Best regards,

János