Page History
...
- About configuring Precise for Microsoft .NET
- About the instrumentation file
- About the ActivityCollector.xml file
- Defining the DLLs to be monitored by using the Detection agent
- Invoking the Instrumentation Driver utility
| Anchor | ||||
|---|---|---|---|---|
|
...
<dll name="System.Messaging.dll">
<instrument>
<classes>
<class>
<name>System.Messaging.MessageQueue</name>
<called-method>
<methods>
<method>
<name>Send</name>
</method>
<method>
<name>Receive</name>
</method>
<method>
<name>BeginReceive</name>
</method>
<method>
<name>EndReceive</name>
</method>
</methods>
</called-method>
</class>
</classes>
</instrument>
</dll>
| Anchor | ||||
|---|---|---|---|---|
|
The ActivityCollector.xml file is the main configuration file of the Microsoft .NET AppTier Collector agent that gathers activity information. It is composed of the following logical sections:
...
| Tag name | Description |
|---|---|
| activity-collector-config | The top-level XML tag. |
| Aggregator | The top-level definitions for the Collector agent’s aggregator. |
| Topnsql | The top number of SQL statements to monitor. |
| Sla | The SLA (red) value (in milliseconds) for ASP.NET instance URLs. |
| nearsla | The Near SLA (yellow) value (in milliseconds) for ASP.NET instance URLs. |
| insane-rt | The timeout value for long running threads/URLs. A method or URL that is longer than this threshold is not collected. |
| tracker | Specific definitions for the tracker. |
| threshold | The threshold (in milliseconds) for filtering events before they are forwarded to the Collector agent. |
| Anchor | ||||
|---|---|---|---|---|
|
A Microsoft .NET instance consists of the DLLs that make up your Microsoft .NET application. For Precise for Microsoft .NET to monitor a Microsoft .NET instance, you must first define the DLLs that you want to monitor.
...
- Open the following file in an editor:
<i3_root>\products\dotnet\config\instrumentation.xml - Within the XML output that you saved in step 5 above, locate the <module name> tag for a DLL file you want to instrument and copy the file name.
For example, if you want to instrument the file petshop.web.dll, copy its name from the line<module name="petshop.web.dll">. - In the instrumentation file, paste the name of the DLL file into the entry for the instance that you want to monitor.
For example:
<instances>
<instance name="AspNetIIS6" >
<dlls>
<dll name="petshop.web.dll"/>
...
</dlls>
</instance>
</instances> - Repeat step 2 and step 3 for each DLL file that you want to instrument.
- Restart your Microsoft .NET application for the changes to take effect.
| Anchor | ||||
|---|---|---|---|---|
|
The instrumentation process is the execution of a Collector agent, which reads the code (the DLLs) of your application and stores an instrumented version in the <i3_root>\products\dotnet\cache\instr cache directory:
...