Vng/issue 1

This is not obvious.

django-raven-metlog has been changed to use the metlog-raven plugin so that we have a simpler method of debugging if metlog is behaving correctly.

The problem is that to integrate smoothly raven.contrib.django, we need to have the DSN set using the SENTRY_DSN entry in Django's settings.py

The DSN is required to extract a project ID by the base class within raven.contrib.django.  

metlog-raven does not have this problem on it's own as the DSN is passed into the metlog plugin and we simply delegate to the underlying raven client.  This has the effect of creating the correct project id for us.

Reworking the django integration to use delegation instead of subclassing is possible but I'd like to minimize the amount of code we have to maintain outside of the core raven library.