• What transactions are monitored at deep-dive level?
  • How long is deep-dive enabled?
  • Should fast running methods be filtered, so we can more easily identify the problems from the noise?
Configure tracing using the following options:
  • Select Transaction(s) - Trace one or more specific Transactions, or select the Performance Collector to globally trace all Transactions coming into the Collector.

    Note

    For a number of reasons, including managing overhead of RTI Monitoring and managing the amount of data that will be collected, we typically recommend tracing only selected Transactions.
  • Ignore Methods – Ignore, don't log, methods that take less than the specified milliseconds. This reduces the overhead that RTI adds to your application as well as eliminating data that may not be useful in solving your problem.
  • Trace Duration
    • Trace for Minutes – Trace for one or more minutes before reverting to Lightweight Transaction Profiling.
    • Trace for Transaction Count – Trace a set number of transactions before reverting to Lightweight Transaction Profiling.
After setting these options, click the Start Trace button to dynamically enable deep dive tracing for the selections. Remember, this happens dynamically so there is no need to recycle your application or do anything else. When this process is complete, you see a message box about the next step:
Dismiss this, and move to the next section which discusses how to gather and analyze deep dive trace data.


loading table of contents...