AppDynamics Application Intelligence Platform

3.8.x Documentation

PDFs

Videos

Release Notes

This topic covers web services exit point configuration. To review general information about monitoring databases and remote services (collectively known as backends) and for an overview of backend configuration see Backend Monitoring. For configuration procedures, see Configure Backend Detection (Java).

Auto-Discovery and Default Naming

Web service backend activity includes all web service invocations. Web service backends are identified using the web service name.

Web Services Configurable Properties

Configurable Properties

Property Used by Default 
in Detection and Naming

Service

Yes

URL

No

Operation

No

Soap Action

No

Vendor

No

Changing the Default Web Service Automatic Discovery and Naming

Depending on exactly what you need to monitor, there may be times when you want to change the default configuration. In most cases, you can generate the right name and the correct number of backends to monitor by editing the automatic discovery rule.

Examples

Web Services Using HTTP for Transport

You can disable automatic discovery of a backend type entirely if this better suits your monitoring needs. For example, if your web services use HTTP for transport and you are fine with them being discovered as HTTP backends, you can disable discovery of the Web Service type backends.

Learn More

  • No labels