I assume the first four are fine because the other SENTRY_CLIENT
options work, and my celerytmp app works (well, I can remotely invoke
it's task.add via the manage.py shell).
I also have this in my settings.py
LOGGING = {
'version': 1,
'disable_existing_loggers': true,
'handlers': {
'sentry': {
'level': 'DEBUG',
'class': 'sentry.client.handlers.SentryHandler',
'formatter': 'verbose'
}
},
'loggers': {
'()': {
'level': 'WARNING',
'handlers': ['sentry']
}
}
}
and I have a view (called "bang_error") that deliberately raises an
exception, so I can reliably reproduce the problem by adjusting one
setting, hitting "bang_error", checking sentry for the error.
I haven't changed MIDDLEWARE_CLASSES from the default (what
django-admin startproject gave me), but obviously I've got a database
and templates confgured. I see from sentry/client/handlers.py that
SentryHandler depends on SentryLogMiddleware, so as a guess I tried
adding it to MIDDLEWARE_CLASSES but it didn't help so I took it out
again.
I have a call to djcelery.setup_loader() at the top of my settings.py
too, I think that's about the last change I made to a fresh django
project. I'm running it via manage.py runserver.
Chris Gough
--
.
Sorry I'm not able to provide more details. But everything was working
with Version: '1.6.0'
I downgraded sentry to 1.6.0 (and added 'paging' and 'indexer' to
INSTALLED_APPS, etc), but basically failed to get this combination of
versions working at all.
Can anyone specify a combination of django/python/sentry/celery
versions that are known to work together?
Chris Gough
--
.