Prevents the current transaction from generating a transaction trace.
This call prevents the current transaction from producing a transaction trace.
You can use this if you have a recurring long-running transaction from which you rarely want to see a transaction trace. However, our algorithm for selecting transaction traces already de-prioritizes traces for transactions that have recently generated a trace. Thus, this call is not usually needed.
To un-suppress a previously suppressed transaction, you would use
You can also prevent a transaction from producing traces with a WSGI environ dictionary. To do se, set the
newrelic.suppress_transaction_trace key for the specific request in the WSGI environ dictionary passed by the WSGI server into the WSGI application being monitored.
Optional. Default is
In this example, you have some URLs or views where your customers often upload files. These frequently slow transactions generate transaction traces more often than is useful, and you'd like to disable transaction traces on these so you will receive more relevant traces.
To disable traces for these transactions, run the following where the transaction is being executed:
If you need more help, check out these support and learning resources:
- Browse the Explorers Hub to get help from the community and join in discussions.
- Find answers on our sites and learn how to use our support portal.
- Run New Relic Diagnostics, our troubleshooting tool for Linux, Windows, and macOS.
- Review New Relic's data security and licenses documentation.