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 error reporting #29

Open
danrademacher opened this issue Sep 4, 2020 · 0 comments
Open

Improve error reporting #29

danrademacher opened this issue Sep 4, 2020 · 0 comments

Comments

@danrademacher
Copy link
Member

danrademacher commented Sep 4, 2020

We have a system in place that sends emails if the ETL script hits an exception.

We confirmed it worked back in March:
image

But then as described in #28 and #25, we have had ongoing import failures that don't cause emails to be sent. I think what we need to do is add more conditions that send emails.

Like if we see error in the API response from CARTO, we should trigger an alert:
2020-09-01T17:23:25.713549+00:00 app[scheduler.3180]: 05:23:25 PM - INFO - {"error":["You are over platform's limits: SQL query timeout error. Refactor your query before running again or contact CARTO support for more details."],"context":"limit","detail":"datasource"}

┆Issue is synchronized with this Asana task

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

No branches or pull requests

1 participant