- System requirements
- Profiler architecture
- Profiler installation
- Uninstall profiler
- Running the profiler
- Profiler activation
- Welcome screen
- Start profiling
- IDE integration
- Profile .NET executable
- Profile ASP.NET application in IIS
- Profile ASP.NET web app on Azure App Service on Linux
- Profile ASP.NET web app on Azure App Service on Windows
- Profile all .NET processes that will start
- Attach profiler to a running application
- Profile remote applications
- AWS SSM
- Direct connect
- SSH access
- Connection broker
- Profiling in Docker container
- Manually enable profiling of local applications
- Agent startup options
- Connect to profiled application
- Profiling overhead
- Snapshots
- Solving performance problems
- CPU profiling
- Thread profiling
- Object allocation profiling
- Memory profiling
- Exception profiling
- Telemetry
- Probes: monitor higher level events
- Inspections: automatic recognition of typical problems
- Automatically trigger actions on event
- Automatic deobfuscation
- Summary, automatic deobfuscation
- Filters
- Profiler command line
- Command line tool to control profiling
- Export of profiling results to external formats
- Profiler .NET API
- Profiler HTTP API
- Settings
- Troubleshooting
SSH access
Profiler uses SSH to log into the remote machine and find all running .NET applications. Both applications running with and without the profiler agent can be found and profiled. If necessary, the profiler will upload the agent to the remote machine and attach it to your application.
Advantages
- Ideal for situations when you have SSH access to the host and want to profile .NET application which runs without a profiler agent.
- No need to configure firewalls and expose ports.
- Ability to profile applications started without the profiler agent using attach.
Prerequisites
-
Remote host must permit SSH port forwarding.
Make sure that
AllowTcpForwarding yes
is set in remote OpenSSH server config, usually at/etc/ssh/sshd_config
on Linux. - The remote user must have a home directory, and it must be writable. The profiler uploads the necessary files to the user's home directory on the remote host. If the home directory is missing or not writable, remote profiling via SSH will fail.
Authentication methods
For authentication on the remote host you can use plain password, SSH private key or SSH agent authentication methods.
