The proxy is the component that connects the agent and the controller. If you can ping the Controller but the agent is not connecting, it is possible that the proxy did not start or that the proxy is not configured correctly. See Resolve PHP Agent Installation Issues and Dynamic Language Agent Proxy.

When the connection is successfully established, log in to the Controller to monitor your application. See Splunk AppDynamics Essentials to get started.

Single Application Per Web Server Instance

This is the default setup assumed by the installer—multiple servers, each with a single application.

Each application has its own agent and its own agent and proxy. There is a single tier and a single node for each application.

Single Application Per Web Server Instance with Multi-Tenant Proxy

This scenario also assumes multiple servers, each with a single application.

In this case, each application has its own agent component but all the agents share a single proxy. There is a single tier and a single node for each application. Sharing a proxy can save some overhead in some situations. See Use a Shared Proxy for PHP Agents.

Multiple Applications on a Single Server

This scenario assumes multiple applications running in a single server.

There is one agent and one proxy supporting multiple applications. By default, the proxy automatically starts when the server starts. The applications can be configured with different tiers and nodes. See Multiple PHP Apps on a Single Server for information on how to configure the Apache vhosts or FPM pool config blocks.