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
Impact of the new feature
Reduce impact on shifter to walk through every WMAgent to check status of all components.
Is your feature request related to a problem? Please describe.
During investigation of DBS3Upload backlog I found that on vocms0282 it was stuck. The ComponentLog shown no issues. We checked with CMS DBA and found that no ORACLE connection was performed either. I logged into docker image and found that this component was not running via manage status command. It means that inspecting ComponentLog is not sufficient to know if component is running or not, and therefore to properly know the status of component the shifter must login to each individual WMAgent docker image, issue manage status command and pay attention about status of the components. In other words,
Describe the solution you'd like
Review how WMStats UI agent info is populated and revisit how we report status of components
Describe alternatives you've considered
Keep things as is and rely on manual checks from shifters.
Additional context
The text was updated successfully, but these errors were encountered:
Impact of the new feature
Reduce impact on shifter to walk through every WMAgent to check status of all components.
Is your feature request related to a problem? Please describe.
During investigation of DBS3Upload backlog I found that on vocms0282 it was stuck. The ComponentLog shown no issues. We checked with CMS DBA and found that no ORACLE connection was performed either. I logged into docker image and found that this component was not running via
manage status
command. It means that inspecting ComponentLog is not sufficient to know if component is running or not, and therefore to properly know the status of component the shifter must login to each individual WMAgent docker image, issuemanage status
command and pay attention about status of the components. In other words,Describe the solution you'd like
Review how WMStats UI agent info is populated and revisit how we report status of components
Describe alternatives you've considered
Keep things as is and rely on manual checks from shifters.
Additional context
The text was updated successfully, but these errors were encountered: