Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve and simplify status check of WMAgent components #12145

Open
vkuznet opened this issue Oct 15, 2024 · 0 comments
Open

Improve and simplify status check of WMAgent components #12145

vkuznet opened this issue Oct 15, 2024 · 0 comments

Comments

@vkuznet
Copy link
Contributor

vkuznet commented Oct 15, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

1 participant