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
{{ message }}
This repository has been archived by the owner on Sep 18, 2020. It is now read-only.
update-agent is typically running on all CL nodes, watching and reacting to update-engine events and annotation. It should expose its status as metrics that can be analyzed and alerted upon. Access to those should be governed by kubernetes RBAC policies.
This is a preliminary list of interesting metrics:
go runtime stats
update-engine status
update-engine last checked time
reboot-needed state
reboot-in-progress state
CL version and channel
The text was updated successfully, but these errors were encountered:
update-agent
is typically running on all CL nodes, watching and reacting to update-engine events and annotation. It should expose its status as metrics that can be analyzed and alerted upon. Access to those should be governed by kubernetes RBAC policies.This is a preliminary list of interesting metrics:
reboot-needed
statereboot-in-progress
stateThe text was updated successfully, but these errors were encountered: