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

How to handle broken/unsupported catalog items - UX #5188

Closed
Tracked by #5677
nf-s opened this issue Jan 28, 2021 · 4 comments
Closed
Tracked by #5677

How to handle broken/unsupported catalog items - UX #5188

nf-s opened this issue Jan 28, 2021 · 4 comments

Comments

@nf-s
Copy link
Contributor

nf-s commented Jan 28, 2021

An idea - Keep track of uptime of catalog items and report to user

Might be a nicer UX than just throwing an error randomly - this would remind users that we don't host the data, and that quite a few services are down frequently

Also, maybe show placeholder for broken or unsupported datasets

@nf-s
Copy link
Contributor Author

nf-s commented Feb 8, 2021

@nf-s nf-s changed the title Keep track of uptime of catalog items and report to user How to handle broken/unsupported catalog items - UX Feb 8, 2021
@t83714
Copy link
Member

t83714 commented Feb 8, 2021

https://sentry.io/for/javascript/

@nf-s
Copy link
Contributor Author

nf-s commented Feb 8, 2021

If we go for the error tracking service option

Pete: We have https://rollbar.com/ setup on some maps already

So see if we can use that - if not look at sentry

@AnaBelgun
Copy link
Member

This ticket is superseded by other error handling tickets:
Only show supported file type in My Data and workbench #5184
Model architecture: Improve preview map #3499
[EPIC] Design and implement error handling #3486

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants