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

Allow client errors marked as "transient" to include link to status page #1777

Open
jhiemstrawisc opened this issue Nov 26, 2024 · 0 comments
Labels
client Issue affecting the OSDF client enhancement New feature or request error messages Improvements to error messages Facilitation A request from the RCF's

Comments

@jhiemstrawisc
Copy link
Member

An interesting thought that goes back to a conversation we had long ago -- if the client encounters a transfer error it believes to be temporary and related to the overall federation (like a director outage), can we find a way to provide a link to a pre-configured status page that may provide information about the outage?

For example, maybe OSPool EPs are configured with some Pelican config so that if a transient error is encountered, the error/hold message has a link to https://status.osg-htc.org. This might help us cut down on the influx of user support tickets that show up any time we touch the Director.

We might also link to the Director itself, because can display origin issues for specific namespaces. If the client gets a 404 no origins found for path /foo/bar, maybe then can check the Director to see that the origin for /foo/bar is having issues.

@jhiemstrawisc jhiemstrawisc added enhancement New feature or request client Issue affecting the OSDF client Facilitation A request from the RCF's error messages Improvements to error messages labels Nov 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
client Issue affecting the OSDF client enhancement New feature or request error messages Improvements to error messages Facilitation A request from the RCF's
Projects
None yet
Development

No branches or pull requests

1 participant