We're using Celery in our Django project and put a CELERY_RESULT_DBURI value (which carries the password to our database) into our settings.py file. Obviously, I don't feel very safe having the password in plaintext in every traceback.
I know about Filtering Error Reports but the only solution I can think of right now is to rewrite the SafeExceptionReporterFilter class by copying the get_traceback_frame_variables() method and monkey-patching CELERY_RESULT_DBURI into it somehow. Does anyone of you know a better solution? How did you work around the problem of exposing the database password?