>From time to time the pager goes off, and I need to find the source of a given query hitting MySQL. It might be poorly performing, or flooding MySQL in high volume. In any case, I'd love some instrumentation that could point me at a lead in my Django site that's more specific than a given user or IP address. I'm considering adding a comment to the query that includes some part of the call stack, possibly based on Ned Batchelder's "global request" code[1]. Is there a community maintained solution to similar problems already in the wild? Or failing that, an approach that the community would like to include in Django?
[1]: http://nedbatchelder.com/blog/201008/global_django_requests.html -- Matt McClure http://www.matthewlmcclure.com http://www.mapmyfitness.com/profile/matthewlmcclure -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/PAcaIZ8CvlUJ. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
