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

tool reporting connectivity issues from the client side #3988

Open
raffaelepotami opened this issue Dec 3, 2024 · 0 comments
Open

tool reporting connectivity issues from the client side #3988

raffaelepotami opened this issue Dec 3, 2024 · 0 comments
Labels
enhancement This is functionality that builds upon existing functionality.
Milestone

Comments

@raffaelepotami
Copy link

Chase Eyster asked me to create this issue related to a recent conversation with the OOD Team during the SC24 conference.

I had a question about troubleshooting Open OnDemand problems reported by the users, which are caused by factors outside what we can control.
For example, we often get users reporting OOD connectivity issues, unresponsive app pages, logout, etc., and in many cases, the route cause is outside our control, like networking/firewall rules from an affiliate institution,
browser issues on the user’s end or even just user behavior.

As of right now, our best option is to check logs under /var/log/ondemand-nginx/$USER, but that is a tedious job,
and I was wondering if there is any plan from OOD to have a built-in tool reporting connectivity issues from the client side, maybe even something visible to the end user like a log of detected connect/disconnect times and errors.

Thank you,
Raffaele

@osc-bot osc-bot added this to the Backlog milestone Dec 3, 2024
@johrstrom johrstrom added the enhancement This is functionality that builds upon existing functionality. label Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement This is functionality that builds upon existing functionality.
Projects
None yet
Development

No branches or pull requests

3 participants