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

Check that logging works when RAVEN_DSN (Sentry) not configured #177

Open
jnm opened this issue May 29, 2018 · 1 comment
Open

Check that logging works when RAVEN_DSN (Sentry) not configured #177

jnm opened this issue May 29, 2018 · 1 comment

Comments

@jnm
Copy link
Member

jnm commented May 29, 2018

From #170:

Fix KC logging for installations that do not use Sentry/Raven. Exception information, including tracebacks, should appear either in the uWSGI or Docker container logs (check KPI's behavior) (see kobotoolbox/kobocat@b55e48f)

Basically: if you don't use Sentry (and have RAVEN_DSN unset in your environment), and you trigger an exception, do you see the error logged anywhere? Check the log files as well as the output of docker-compose logs. If the error doesn't appear, then we have a problem with our logging setup (and probably need to file bugs against kpi and kobocat).

@noliveleger
Copy link
Contributor

@jnm it does not show anything in the logs except with DEBUG is True.

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

2 participants