Fully featured low overhead profiler for Java EE and Java SE platforms.
Monitoring and profiling solution for Gradle, Maven, Ant, JUnit and TestNG.
Easy to use performance and memory profiler for .NET framework.

Remote profiling from user interface

To profile Java applications running on the remote machine use Profile remote Java EE server or application... action on Welcome screen or in "Tools" menu.

Specify the host name or IP address of the remote machine in the opened "Profile Remote Application" dialog.

Application discovery method

There are two methods for detecting applications running on the remote machine:

  • Simple method. Profiler discovers applications running with the profiler agent. Ports in the given range will be scanned. By default the profiler agent port is allocated in the range 10001-10010. If the profiler port was changed with startup option 'port', also change the Profiler agent port(s) field accordingly.

  • Advanced method. Profiler creates SSH connection to the remote machine. It will detect all running Java applications. Applications running without the profiler agent will be detected as well. You will be able to attach to them. Specify SSH user and SSH port in the corresponding fields. Authentication with a password or a private key is supported.

Why advanced method is better?

  • Uses SSH protocol for secure network communication.
  • No need to configure firewalls and expose ports.
  • Automatically uploads profiler agent and all other necessary files.
  • Ability to profile applications started without the profiler agent using attach.

SSH tunnel

If the remote host is not directly reachable you can build SSH tunnel. To do so, navigate to the SSH Tunnel tab and enable SSH tunnel using Use SSH tunnel checkbox.

Connect to remote application

Created connection will appear in the "Monitor Applications" list on Welcome screen under a given name. You can then connect to the application to perform profiling.

If you do not see your application it the list, please read Troubleshoot connection problems.

For a usage example see Profiling in Amazon EC2 instance.

Please note that for SSH connections known hosts are not checked, and StrictHostKeyChecking SSH parameter is set to no.