Fully featured low overhead profiler for Java EE and Java SE platforms.
Performance monitoring and profiling of Jenkins, TeamCity, Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Attaching agent to running application

Attach technique allows to load the profiler agent into running .NET runtime, but attached agent has several limitations in functionality. Attach is available in .NET Framework 4 or newer.

Attach from Welcome screen

All detected locally running .NET applications are shown in the "Monitor Applications" list on Welcome screen. The colored circle indicates the profiler agent status. When agent is already loaded the circle is green. Orange circle shows that agent is not yet loaded but can be attached.

Attach from command line

Run the command line tool to attach profiler agent and then connect from Welcome screen.

Attach mode limitations

Not all profiling capabilities are available in the attach mode due to .NET Framework limitations listed below. To get all capabilities, application should be started with the profiler.

  • Memory profiling is disabled for applications running in concurrent GC mode. Read this MSDN article to learn how to avoid using concurrent GC mode.
  • CPU tracing is not available. Use sampling instead.
  • Some threads started before attach will not be shown. In particular, they will not be seen in the Threads view and in CPU sampling results. To make some of the threads appear, you may try to explicitly force garbage collection via corresponding toolbar button.
  • Object allocation recording is disabled
  • Exception telemetry is disabled
  • Event recording with Probes is not available