The .NET Exception Sensor instruments the exception’s constructor to retrieve information about the exception’s class, its message, and optionally its stack trace elements. It also retrieves information about exceptions that do not get “thrown” but are created via
new. The transferred exception event is handled as a single event with no duration.
To edit the System Profile specific settings, right click you System Profile, and select Edit System Profile > Agent Group/tier with .NET technology > Sensor Configuration and then select the .NET Exception item in the Sensor Configuration list.
Exception aggregation is aimed to reduce the PurePath node count when many exceptions are thrown. The aggregation is done per instrumented node level. The first three exceptions are captured normally, beginning with the 4th exception, aggregation will take effect and only count occurrences of distinct class+message combinations.
You can define which classes to instrument. There are two possible scenarios:
- Instrument listed classes only.
- Instrument all classes, except for the listed ones.
Select the appropriate option button and list classes to be included/excluded from the instrumentation. You can do this manually or use the Class Browser.
In the Overhead Properties section in the Exception Sensor Properties dialog box, you can enable or disable capture of stack traces for exceptions and fine-tune the amount of data that is captured and transferred from the Agent to the Server.
|Overhead Property||Description||Overhead impact||Default value|
Enables capturing of stack traces. |
Capturing the stack and transferring the data to the server causes high CPU overhead on the instrumented application and consumes network bandwidth.
|Maximum Captured Stacktrace depth||
Limits the number of elements per stacktrace. Only the topmost elements are transferred.|
The allowed range is 0—256.
|Maximum Captured Stacktraces per second||
Limits the number of stacktraces captured per second.|
The allowed range is 0—1024.