Page History
...
When we discuss configuring Precise for Microsoft .NET, we talk about two sections:• Dynamic
- Dynamic instrumentation
...
- Tracking instrumentation activity
The Microsoft .NET AppTier Collectors agents use the dynamic instrumentation of your Microsoft .NET-based applications to track software activities that are based on Microsoft .NET. Therefore, the instrumentation configuration determines the tracking quality, the amount of overhead involved, and whether the data collected really suits your specific needs.
...
The rules for dynamic instrumentation configuration are defined in the following files:
- instrumentation.xml.
...
- This file contains explicit instrumentation rules for the tracked instances
default-instr-config.
...
xml. This file contains the default instrumentation rules for the tracked instances.
Info
...
Do not modify this file without consulting Precise Technical Support.
...
- ActivityCollector.xml. This file contains the configuration of the Microsoft .NET AppTier Collector agent, which determines other tracking rules, including implicit instrumentation rules.
Limitations of tracking instrumentation activity
Tracking instrumentation activity is subject to the following limitations:• Only
- Only the Microsoft .NET version 1.1, 2.0, 3.0, and 3.5 Frameworks are supported.
...
- The time resolution (granularity) of the tracked activity is approximately 16 milliseconds.
...
Certain system DLLs that are part of the Microsoft .NET infrastructure cannot be instrumented. It is strongly recommended not to add an additional system DLL to the DLL list without first contacting Precise Technical Support.
Info
...
All system DLLs that are discussed, are safe for instrumentation.
...
- Generated Microsoft .NET wrappers for COM+ components that are produced by Microsoft .NET Framework SDK utilities (such as TLBImp) cannot be tracked.
...
- "Pre-Jitted" assemblies cannot be instrumented because they were compiled beforehand. For example, the System.Windows.Forms.dll is pre-jitted in the Microsoft .NET framework.
| Anchor | ||||
|---|---|---|---|---|
|
The Instrumentation.xml file is located in the <i3_root>\products\dotnet\config directory. It contains the following major section:• Instance
- Instance-specific section
Following is an example of the file structure:
<?xml version="1.0" encoding="utf-8"?>
<instrumentation-config>
<instances>
<instance name="Instance_A">
Instance A instrumentation rules
</instance>
<instance name="Instance_B">
Instance B instrumentation rules
</instance>
</instances>
</instrumentation-config>
The file consists of the following subsections:• DLL
- DLL list: A list of DLLs to be instrumented and specific configuration rules for each DLL. If the underlying process of the instance should be instrumented, it must be mentioned explicitly.
...
- Common instrumentation rules (“instrument”) for the whole DLL list.
...
- Common exclude rules (“ignore”). Following is an example of the file structure:
<dlls>
<dll name="dll_A_name" />
<dll name="dll_B_name" />
<dll name="dll_C_name" >
<instrument>
Specific instrumentation rules for DLL C.
</instrument>
<ignore>
Specific ignore rules for DLL C.
</ignore>
</dll>
<dll name="dll_D_name" >
<instrument>
Specific instrumentation rules for DLL D.
</instrument>
<ignore>
Specific ignore rules for DLL D.
</ignore>
</dll>
</dlls>
<instrument>
Common instrumentation rules for all the DLLs in this context (A, B, C, D).
</instrument>
<ignore>
...
Common ignore rules for all the DLLs in this context (A, B, C, D).
</ignore>
Example of the instrumentation.xml file
...