AppDynamics Application Intelligence Platform

3.9.x Documentation


Learn by Watching

Doc Maps

Skip to end of metadata
Go to start of metadata

Service Endpoints for Monitoring Specific Services

In complex, large-scale applications, some application services may span multiple tiers. If you own an application service, you may need metrics on that specific service as opposed to metrics from across an entire business transaction or entire tier.  Service endpoints allow you to obtain a subset of metrics and associated snapshots for your service so that you can focus on the information truly of interest to you.

Using service endpoints, you can define a set of entry points into your specific service to create a customized view in the AppDynamics UI that displays the key performance indicators, associated snapshots, and metrics that affect only that service.  You can understand the performance of your service and quickly drill down to snapshots that affect your service, instead of sifting through snapshots for the entire tier or business transaction.


Understand Service Endpoints 

Service endpoints are similar to business transactions except that they report metrics only at the entry point and do not track metrics for any downstream segments. Service endpoints are not automatically detected like business transactions are detected; you must specify the entry points for service endpoints. Service endpoints support the same entry point types as business transactions and you configure them in a similar way. 

Snapshot information for the service endpoint refers back to the originating business transaction snapshot that goes through service endpoint-defined entry points.

All normal metric operations of metrics are observed for metrics collected by the service endpoint; this includes metrics registration and metric rollups for tiers, limits on number of metrics, and other standard operations. Captured metrics for service endpoints are limited to entry point metrics. Custom metrics are not supported on service endpoints.

Diagnostic sessions cannot be started on the service endpoints; however, you can create diagnostic sessions on the originating business transaction.

Service endpoints are supported for the Java Agent and the .NET Agent.

Additional load on the system for service endpoints is negligible. For example, with 1000 agents, additional metric traffic amounts to only 30K. Approximately three metrics are captured per service endpoint and the agent has a default limit of 100 service endpoints. This limit is configurable using the max-service-end-points-per-node node property.

Service Endpoint Metrics in the UI

Key Performance Indicators and Transaction Scorecard

  1. On the left-hand navigation menu, click a Tier.
  2. On the right-hand side of the Tier Flow Map, click Service Endpoints

    Key performance indicator metrics along with transaction scorecards display.

    The information displayed relates only to the service endpoints entry points defined for the tier. 
    (info) If the Service Endpoints tab does not display, it means that there are no endpoints configured or that they are not reporting data.

  3. Double-click a service endpoint name to see the Service Endpoints Transaction Snapshots.
  4. Click the snapshot or double-click the Business Transaction, Tier, or Node links for additional details. These details help you to troubleshoot problems with your service.

Service Endpoints in the Metric Browser

At a glance, you can see the performance of your service by looking at the service endpoints in the Metric Browser.

To configure service endpoints for your business application see Configure Service Endpoints.

 Learn More