- 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
- 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
AWS SSM
If you already use AWS CLI to connect to AWS instances, this method may be a better alternative to the SSH access method. Knowing just the instance ID, profiler will use AWS CLI with SSM plugin to log into the instance and find all running .NET applications.
Advantages
- Ideal for profiling .NET applications running on an AWS instance.
- Connect to the AWS instance using instance ID.
- No need to expose SSH port.
- Ability to profile applications started without the profiler agent using attach.
Prerequisites
- AWS CLI installed and configured on the local machine.
- Session Manager plugin for the AWS CLI.
- AWS instance with SSM agent .
-
AWS instance must permit SSH port forwarding.
Make sure that
AllowTcpForwarding yesis set in remote OpenSSH server config, usually at/etc/ssh/sshd_configon Linux.
Authentication methods
For authentication on the instance you can use plain password, SSH private key or SSH agent authentication methods.
