allura-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From brond...@apache.org
Subject [allura] 01/02: [#8276] hook up new relic error tracing now that its builtin pylons tracing doesn't apply
Date Thu, 11 Apr 2019 22:11:11 GMT
This is an automated email from the ASF dual-hosted git repository.

brondsem pushed a commit to branch db/8276b
in repository https://gitbox.apache.org/repos/asf/allura.git

commit a89bc93066a2ef3c6e3e6562b56866fb6ebce2c6
Author: Dave Brondsema <dave@brondsema.net>
AuthorDate: Thu Apr 11 18:07:42 2019 -0400

    [#8276] hook up new relic error tracing now that its builtin pylons tracing doesn't apply
---
 Allura/allura/lib/patches.py | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/Allura/allura/lib/patches.py b/Allura/allura/lib/patches.py
index 9e1734a..ab58968 100644
--- a/Allura/allura/lib/patches.py
+++ b/Allura/allura/lib/patches.py
@@ -125,3 +125,6 @@ def newrelic():
         newrelic.agent.set_transaction_name(
             newrelic.agent.callable_name(controller))
         return old_controller_call(self, controller, *args, **kwargs)
+
+    import newrelic.api.error_trace
+    newrelic.api.error_trace.wrap_error_trace('tg.wsgiapp', 'TGApp.__call__')
\ No newline at end of file


Mime
View raw message