Customize Xamarin Automatic Instrumentation

Customize Automatic Network Request Instrumentation

When automatic network request instrumentation is enabled, the weaver will search the project for all new instances of HttpClient or Refit usages. In instances that are found, the agent instrumentation code will be injected to the HttpClient or Refit request.

You can further customize the automatic instrumentation at the project level or class level (see sections below). For example, you could:

1. Enable the automatic instrumentation at a project level from the FodyWeavers.xml file, but exclude some files at the class level using the DisableNetworkInstrumentation attribute.

2. Disable the automatic instrumentation at a project level from the FodyWeavers.xmlfile, but includesome files at the class level using the EnableNetworkInstrumentation attribute.

Enable/Disable at the Project Level

You can enable or disable automatic instrumentation at the project level using the NetworkInstrumentationEnabled flag in the FodyWeavers.xml file.

For example:

<Weavers xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FodyWeavers.xsd">
... Existing weavers ...
<AppDynamics.Agent.AutoInstrument NetworkInstrumentationEnabled="true"/>
</Weavers>

Enable/Disable at the Class Level

You can enable or disable automatic instrumentation at the class level by using one of the following attributes per class:

1. [EnableNetworkInstrumentation]

   JAVACopy

   [EnableNetworkInstrumentation] public class MyClass { ... }

   [EnableNetworkInstrumentation]
   public class MyClass
   {
   ...
   }

2. [DisableNetworkInstrumentation]

   JAVACopy

   [DisableNetworkInstrumentation] public class MyClass { ... }

   [DisableNetworkInstrumentation]
   public class MyClass
   {
   ...
   }

Recommendations

• If you are using DisableNetworkInstrumentation manual network request tracking, you will see duplicate entries for the same network request. To avoid this, you can either remove the manual instrumentation or use the

• If your HTTP requests are handled in a different project, you should add both the AppDynamics.Agent and AppDynamics.Agent.AutoInstrument.Fody to that project as well for instrumentation to work.
• If you are using a HttpClient instance generated in another library, you should only create and use the instance within the same project for instrumentation to work. Automatic instrumentation works by targeting new HttpClient instances within the project.

Customize Automatic Page Tracking Instrumentation

When automatic page tracking instrumentation is enabled, the weaver will search the project for all instances of Xamarin.Forms Page in the project and inject the instrumentation code.

Enable/Disable at the Project Level

You can enable or disable automatic Page Tracking instrumentation at the project level using the PageTrackingInstrumentationEnabled flag in the FodyWeavers.xml file:

<Weavers xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FodyWeavers.xsd">
... Existing weavers ...
<AppDynamics.Agent.AutoInstrument PageTrackingInstrumentationEnabled="true"/>
</Weavers>

Enable/Disable at the Class Level

You can enable or disable automatic instrumentation at the class level by using one of the following attributes per class:

1. [EnablePageTracking]

   JAVACopy

   [EnablePageTracking] public class MyPage : Xamarin.Forms.ContentPage { ... }

   [EnablePageTracking]
   public class MyPage : Xamarin.Forms.ContentPage
   {
   ...
   }

2. [DisableUITRacking]

   JAVACopy

   [DisablePageTracking] public class MyPage : Xamarin.Forms.ContentPage { ... }

   [DisablePageTracking]
   public class MyPage : Xamarin.Forms.ContentPage
   {
   ...
   }

Automatic UI Tracking Instrumentation

When automatic UI tracking instrumentation is enabled, the weaver will search the project for all instances of Xamarin.Forms Button, Entry and ListView in the project and inject the instrumentation code.

Enable/Disable at the Project Level

You can enable or disable automatic instrumentation at the project level using the UITrackingInstrumentationEnabled flag in the FodyWeavers.xml file.

For example:

<Weavers xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FodyWeavers.xsd">
... Existing weavers ...
<AppDynamics.Agent.AutoInstrument UITrackingInstrumentationEnabled="true"/>
</Weavers>

Enable/Disable at the Class Level

You can enable or disable automatic instrumentation at the class level by using one of the following attributes per class:

1. [EnableUITracking]

   JAVACopy

   [EnableUITracking] public class MyPage : Xamarin.Forms.ContentPage { ... }

   [EnableUITracking]
   public class MyPage : Xamarin.Forms.ContentPage
   {
   ...
   }

2. [DisableUITRacking]

   JAVACopy

   [DisableUITracking] public class MyPage : Xamarin.Forms.ContentPage { ... }

   [DisableUITracking]
   public class MyPage : Xamarin.Forms.ContentPage
   {
   ...
   }

Automatic UI Tracking and XAML

Automatic UI Tracking works with both XAML and code-behind UI elements. But even though code-behind UIs are automatically instrumented, there's a required extra step to auto-instrument XAML. Add the following configuration to your .csproj file:

<PropertyGroup>
<FodyDependsOnTargets>
XamlC
</FodyDependsOnTargets>
</PropertyGroup>

Automatic UI Tracking only works with pre-compiled XAML, so you will need to use XamlCompilationOptions.Compile:

[XamlCompilation(XamlCompilationOptions.Compile)]

By default, a project created with a Visual Studio Xamarin.Forms template will already include this. See XAML Compilation in Xamarin.Forms for more information.