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
On Kubernetes cluster one of Pods was manually restarted and we didn't receive any metrics that can indicate that restart because telegraf has take metrics directly in the moment when no valid containers were in v1.Pod.Status.ContainerStatuses.
Respective piece of code:
For some valid reasons (for example Network issues) it could be that p.Status.ContainerStatuses is empty and we will not receive any metrics at all until issue will be resolved, as in above example of restarting Pod.
Relevant telegraf.conf:
System info:
Telegraf version 1.15.2
Steps to reproduce:
On Kubernetes cluster one of Pods was manually restarted and we didn't receive any metrics that can indicate that restart because telegraf has take metrics directly in the moment when no valid containers were in
v1.Pod.Status.ContainerStatuses
.Respective piece of code:
For some valid reasons (for example Network issues) it could be that
p.Status.ContainerStatuses
is empty and we will not receive any metrics at all until issue will be resolved, as in above example of restarting Pod.Expected behavior:
Actual behavior:
Additional info:
PR: #8472
The text was updated successfully, but these errors were encountered: