Documentation forAppOptics

Remote Services

AppOptics automatically tracks RPCs and other remote calls made by the instrumented application. Remote Services provides you with the tools to analyze and troubleshoot frequent and poorly-performing calls to remote services.

apm_remote_services

How remote services are classified

Three tags are gathered for remote service calls, each of which can be used to group/filter the data:

  • Remote service identifier - remote_service
    • For an AppOptics-instrumented downstream service, this will be the name of the remote service (for example: my_analytics_service)
    • For a 3rd-party or uninstrumented service, this will be the hostname or IP of the remote service
  • Service operation - remote_service_op
    • The type of operation being performed
    • For HTTP requests, this will be the HTTP method (for example: get)
    • For GPRC, this will be the remote method being invoked
  • Service type - remote_service_type
    • The type of remote service–HTTP, HTTPS, GRPC, etc.

Drilling down

The data can be filtered using the controls at the top of the page, and you can also drill down to traces of requests that made a particular RPC call by selecting Traced Remote Calls in the drop down to the right:

apm_remote_services_traces

The data in this view is gathered from sampled transaction traces, so it can all be mapped to example traces. Read more about sampling.

When the APM Integrated Experience is enabled, AppOptics shares a common navigation and settings with the other integrated experiences' products. How you navigate AppOptics and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.