If instrumenting an application that is not also handling web traffic, you won't need to wrap the WSGI application entry point. If the task to be tracked is running in a background thread of an existing monitored web application process, then initialization of the agent would already be performed so you shouldn't need to repeat this step. This is the same process described in Standard Python install for a web application. The first requirement is getting the agent initialized and running with the process to be monitored. The Python agent also has built-in instrumentation for the task-queuing systems Celery and Gearman. These transactions show up as non-web transactions in the New Relic UI. The Python agent is mainly designed to monitor web apps and their web requests, and therefore it includes built-in instrumentation for WSGI-based web apps and popular web frameworks.īut you can also monitor arbitrary job-based systems, standalone scripts, worker processes, and non-web transactions using the background_task method.
0 kommentar(er)
