Application Dependency Mapping (ADM) for Discovery

Application Dependency Mapping (ADM) creates relationships between interdependent applications.

ADM identifies:
  • The devices that are communicating with one another.
  • The TCP ports these devices are communicating on.
  • The processes that are running on these devices.

For example, if a web server application uses a database server application, the web server "depends on" the database. The web server also "runs on" the host or server cluster. You can use the data from running processes to determine which devices to drill into to see more application-specific configuration data.

You can disable ADM and use the ADM probes and sensor to collect active connections and active process information without collecting all the Application Dependency Mapping information.

Discovery ADM probes and sensors

ADM uses the following probes:
Table 1. ADM Probes
Name Probe Type Description Includes Probes
AIX - ADM Multiprobe Queries for information about active (running) AIX processes and active connections - the information required to perform application dependency mapping.
  • AIX - Active Connections
  • AIX - Active Processes
HP-UX - ADM Multiprobe Queries for information about active (running) HP-UX processes and active connections - the information required to perform application dependency mapping.

This probe requires that lsof be installed and the UNIX - Active Connections probe be activated, which is inactive by default.

  • UNIX - Active Connections
  • HP-UX - Active Processes
Solaris - ADM Multiprobe Queries for information about active (running) Solaris processes and active connections - the information required to perform application dependency mapping. This probe is triggered by the Solaris Zones probe. The system triggers an ADM probe for each local zone contained in a global zone.

This probe requires that lsof be installed on the global zone.

Solaris - Active Processes

Solaris - Active Connections

UNIX - ADM Multiprobe Queries for information about active (running) UNIX processes and active connections - the information required to perform application dependency mapping.
  • UNIX - Active Connections
  • UNIX - Active Processes
Windows - ADM Multiprobe Queries for information about active (running) Windows processes and active connections - the information required to perform application dependency mapping.
  • Windows - Active Connections
  • Windows - Active Processes
ADM uses the following sensors:
Table 2. ADM Sensors
Name Sensor Type Description Responds to Probes Probes
AIX - ADM Javascript Updates the running processes and active connections, and runs application dependency mapping.
  • UNIX - Active Connections
  • AIX - Active Processes
HP-UX - ADM Javascript Updates the running HP-UX processes and active connections, and runs application dependency mapping. This sensor requires that lsof be installed.
  • UNIX - Active Connections
  • HP-UX - Active Processes
Solaris - ADM Javascript Updates the running Solaris processes and active connections, and runs application dependency mapping. This sensor requires that lsof be installed.
  • Solaris - Active Processes
  • Solaris - Active Connections
UNIX - ADM Javascript Updates the running Unix processes and active connections, and runs application dependency mapping.
  • UNIX - Active Connections
  • UNIX - Active Processes
Windows - ADM Javascript Updates the running Windows processes and active connections, and runs application dependency mapping.
  • Windows - Active Connections
  • Windows - Active Processes

Requirements for ADM

Your instance must meet the following requirements to use application dependency mapping:
  • The glide.discovery.application_mapping Discovery property is enabled.
  • ADM probes are configured.
  • Process classifiers are configured.