Navigation Menu

Skip to content
This repository has been archived by the owner on Mar 15, 2018. It is now read-only.

bug 822759 - fixes for enabling the metlog client @ settings.METLOG #548

Merged
merged 1 commit into from Jan 3, 2013

Conversation

crankycoder
Copy link
Contributor

  • switched settings back to having METLOG_CONF set in one place
  • bumped django-raven-metlog and metlog-raven revisions for more
    consistent configuration
  • renamed USE_METLOG_FOR_RAVEN to USE_METLOG_FOR_TASTYPIE for clarity
  • enabled tastypie logging through metlog
  • set the SENTRY_CLIENT so that all raven messages are routed through
    metlog
  • removed the dual loggers in the explode() function of generate-error. Just use the one true logger in settings.METLOG

* switched settings back to having METLOG_CONF set in one place
* bumped django-raven-metlog and metlog-raven revisions for more
  consistent configuration
* renamed USE_METLOG_FOR_RAVEN to USE_METLOG_FOR_TASTYPIE for clarity
* enabled tastypie logging through metlog
* set the SENTRY_CLIENT so that all raven messages are routed through
  metlog
@@ -24,7 +24,7 @@ django-mysql-pymysql==0.1
django-nose==1.1
django-picklefield==0.2.1
django-quieter-formset==0.3
django-raven-metlog==0.1
django-raven-metlog==0.2
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

django-raven-metlog 0.2 has been added to pyrepo1

kumar303 added a commit that referenced this pull request Jan 3, 2013
bug 822759 - fixes for enabling the metlog client @ settings.METLOG
@kumar303 kumar303 merged commit 35138c7 into mozilla:master Jan 3, 2013
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants