Developers use .NET remoting to build distributed applications that share objects across processes or across application domains running in the same process. AppDynamics disables correlation for .NET remoting functions by default.
Instrument Applications That Use .NET Remoting
You can configure the .NET Agent to discover .NET remoting entry and exit points.
config.xmlfile for editing as administrator. See 'Where to Configure Agent Properties' on Administer the .NET Agent
Copy the code block below to a child element of the Machine Agent element. See .NET Agent Configuration Properties
- Save the
- Restart the
- Restart instrumented applications for your changes to take effect.
If the agent does not discover the entry points after configuration, specify an agent trigger.
Specify an Agent Trigger
.NET remoting entry point functions execute in low-level .NET libraries that may not trigger automatic agent instrumentation. If the agent does not discover the .NET remoting entry points after configuration you can specify a function that triggers the agent to begin instrumentation.
Identify a function to trigger the agent to begin instrumentation. The function can be any function that executes as part of the application process.
For example, consider the following code for a
MovieTicketremoting object. In this case, use the function
GetTicketStatusto trigger the agent.
config.xmlfile as an administrator. See Administer the .NET Agent
Update the Instrumentation element to include the
AgentTriggerInstrumentorattribute. See .NET Agent Configuration Properties
argsvalue to the name of the trigger function, using information in the code block in step 1. The
argsvalue should be formatted as follows:
- Save the
Restart instrumented applications for your changes to take effect.