Reporting should use the django logging framework #18

Closed
graingert opened this Issue Jul 17, 2012 · 2 comments

Comments

Projects
None yet
2 participants
@graingert
Contributor

graingert commented Jul 17, 2012

https://docs.djangoproject.com/en/dev/topics/logging/

"A logger can have multiple handlers, and each handler can have a different log level. In this way, it is possible to provide different forms of notification depending on the importance of a message. For example, you could install one handler that forwards ERROR and CRITICAL messages to a paging service, while a second handler logs all messages (including ERROR and CRITICAL messages) to a file for later analysis."

Rather than hardcoded email support, use the standard logging framework

@graingert

This comment has been minimized.

Show comment Hide comment
@graingert

graingert Aug 7, 2012

Contributor

It would also be possible to move the de-duplication code to a logging handler:

https://docs.djangoproject.com/en/dev/topics/logging/#topic-logging-parts-handlers

Contributor

graingert commented Aug 7, 2012

It would also be possible to move the de-duplication code to a logging handler:

https://docs.djangoproject.com/en/dev/topics/logging/#topic-logging-parts-handlers

@jsocol

This comment has been minimized.

Show comment Hide comment
@jsocol

jsocol Jun 7, 2013

Member

Closing in favor of #30.

Member

jsocol commented Jun 7, 2013

Closing in favor of #30.

@jsocol jsocol closed this Jun 7, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment