- Print
- DarkLight
- PDF
Runtimes Supported
.NET Full Framework
- v4.5.2 (built targetting 4.5.2, but must run under CLR 4.6.1)
- v4.6.1 and later
. NET Core
- v2.1 and later (2.1 and 3.1)
.NET
- v5.0
For older runtimes/frameworks, see the list of Legacy Profiler Supported Technologies
Application Types
- ASP.NET Web Applications
- ASP.NET Core Web Applications
- Windows Services
- Command line applications and services
Command line applications and services will need custom instrumentation to track operations unless the application just runs tasks via Quartz.Net scheduling.
Installing the Windows Agent
Make sure that the Windows Retrace Monitoring Agent is installed on your host and the Profiler has been enabled:
Reference the Retrace Windows Install article for more detailed information on installing the agent.
Naming Your App
Create a file named Stackify.json
and save it in the deployment folder of your application.
{
"AppName": "MyApp",
"Environment": "Production"
}
Sending All Exceptions to Retrace
By default the profiler only captures "unhandled" exceptions to avoid the overhead of a first-chance exception handler. However, if you want to capture and upload all first-chance exceptions you can enable this on a per application basis. To enable this, add the setting CaptureAllExceptions
to the Stackify.json
file as shown in the following example.
{
"AppName": "MyApp",
"Environment": "Production",
"CaptureAllExceptions": true
}
Disabling Tracing
If you want to temporarily disable collection of APM data, you can add a property to the Stackify.json
file to cause the profiler to be disabled. This does not impact collection of logs that are sent to Retrace.
{
"AppName": "MyApp",
"Environment": "Production",
"DisableTracing": true
}