This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.

Skip to end of metadata
Go to start of metadata

On this page:

Related pages:

Configure custom service endpoints in AppDynamics to monitor the performance of an entry point for a service or application on a single tier.

By default you have to restart the instrumented application for instrumentation changes like a new POCO service endpoint to take effect. You can enable Runtime Reinstrumentation for the .NET Agent so that you don't need to restart your application and the AppDynamics.Agent.Coordinator after instrumentation changes.

For example, consider a Travel site that has an ASP.NET MVC front end. When a customer searches, the /Travel/Search business transaction originates on the MVC tier that calls a WCF service. The WCF service in turn calls external travel sites, aggregates the results, and returns the search results to the MVC front end.

If you are solely responsible for the HWT Core Services tier or the WCF service, a service endpoint lets you focus on the performance metrics that apply to your tier.

The .NET Agent doesn't automatically discover service endpoints. To define a custom service endpoint for .NET navigate to Configuration > Instrumentation > Service Endpoints > Custom Service EndpointsDefine the service endpoint as you would a custom match rule for a business transaction. See Service Endpoints and Business Transaction Detection.

You can create service endpoints for the following entry point types:

Message Queues
Web Service

The .NET Agent doesn't support service endpoints for MSMQ.


After you configure a custom service endpoint, you can monitor it on the service endpoint dashboard that shows KPIs and transaction snapshots where the service endpoint executed. You can also use the metric browser to analyze service endpoint performance. See Service Endpoints.

Tips for Defining .NET Service Endpoints

Although the .NET Agent doesn't automatically discover service endpoints, frequently you want to monitor service endpoints that match automatically discovered entry points in a business transaction:

  • You can create service endpoints on the originating entry point for a business transaction.
  • For ASP.NET service endpoints, you can use the URL.

For example, in the Travel Site tier above: URL matches "/Travel/Search"

  • For WCF and ASP.NET web service entry points, you can use an existing transaction snapshot to find the URL for the service.
    1. Open a full transaction snapshot for the business transaction.
    2. From the upstream tier, click the exit call link, either WCF or Web Service.
      The exit call window shows the URL for the web service.
    3. Open the service URL in a browser.
    4. On the service page, the url to access the wsdl file.
    5. The service name element shows the service name.

      <wsdl:service name="Service1">
  • Define POCO service endpoints exactly as you would a POCO custom match rule.