Object Instance Tracking for .NET
This page describes how to enable object instance tracking on a node. When you enable object instance tracking on a node, Splunk AppDynamics analyzes the heap to identify classes with the most instances on the heap. Splunk AppDynamics tracks the top 20 .NET framework classes and the top 20 application classes based on the number of instances. Use object instance tracking to identify memory usage trends in classes with a large number of instances.
Permissions
To enable object instance tracking, you need one of these permissions:
- Configure Memory Monitoring
- Configure Agent Properties
Limitations
Object Instance Tracking is not supported on Windows Nano.
Prerequisites
- If you are not using MSI for the agent installation, make sure you copy the following files.
- On Linux:
AppDynamics.HeapDump.Library.dll
- On Windows:
AppDynamics.HeapDump_x86.dll
andAppDynamics.HeapDump_x64.dll
- On Linux:
-
On Linux, ensure that applications have the required permission to perform
ptrace
calls. In Docker Linux containers, the following command argument will enable theSYS_PTRACE
capability.--cap-add SYS_PTRACE
Enable Object Instance Tracking on a Node
Identify Memory Usage Problems
Use these guidelines to identify memory usage problems:
- The Controller resolution for object instances is one minute, but the .NET Agent only sends data every ten minutes, so .NET memory appears as a series of peaks over time.
- It is normal for the Controller to display 0 for the Current Instance Count and Shallow Size in between instance count collection times.
- Hover over a peak to display information about the instance count.
- Look for trends where the peaks increase in size from left to right which may indicate a memory leak.