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
What would you like to be added:
Reboot history as part of the eks-log-collector script.
Why is this needed:
There are cases where a hard reboot has affected service processes, but this is not clearly evident in the collected logs.
We have been debugging containerd and various other components with AWS Support to determine why they're being restarted. At first approach this was thought to be an issue at the container level (CNI), but looking outside the logs we've discovered that a hard reboot has been interrupting everything:
reboot system boot 6.1.102-108.177. Sun Aug 11 01:16 still running
reboot system boot 6.1.102-108.177. Sun Aug 11 01:15 still running
This isn't clear in the current export via dmesg either because it only tracks the current session.
It would be helpful to have these logs included so that reboots can be quickly correlated with any service interruptions.
The text was updated successfully, but these errors were encountered:
What would you like to be added:
Reboot history as part of the eks-log-collector script.
Why is this needed:
There are cases where a hard reboot has affected service processes, but this is not clearly evident in the collected logs.
We have been debugging containerd and various other components with AWS Support to determine why they're being restarted. At first approach this was thought to be an issue at the container level (CNI), but looking outside the logs we've discovered that a hard reboot has been interrupting everything:
This isn't clear in the current export via dmesg either because it only tracks the current session.
It would be helpful to have these logs included so that reboots can be quickly correlated with any service interruptions.
The text was updated successfully, but these errors were encountered: