The NGINX Agent monitors NGINX Webservers. Depending on the agent platform you use, its architecture and functionality may differ. Find the detailed information below.
See Configure NGINX Agent to learn how to configure the Agent.
The NGINX Agents consists of two parts:
- The NGINX Agent Server Module (slave) is the module that is loaded by the web server. It gathers the information that is used for analysis on the AppMon Server.
- The Web Server Master Agent is a separate process that collects data of all worker processes (slaves). It handles communication with the Collector and retrieves configuration data among other functions. See Web Server Maser Agent configuration to learn how to configure this master agent.
The NGINX Agent communicates with the Master Agent through these channels:
- A shared memory segment propagates configuration data, received from the Collector by the Master Agent, to the worker processes and to hold other information that must be shared across all worker processes. The shared memory segment is backed by a file in
<DT_HOME>/agent/confon all platforms where the worker processes and the Agent process must have read/write access.
- The NGINX Agents (slaves) send collected data to the Master Agent through a stateless UDP connection. The Master Agent collects the data, transforms it, and forwards it to the Collector (standalone or Server-embedded).
The NGINX consists only of a NGINX Agent Server Module that is loaded by the web server. It collects data of all worker processes. It gathers the information that is used for analysis on the AppMon Server. The AppMon Agent is responsible for handling communication with the Collector. Find more information about AppMon Agent platform here.
To use AppMon Agent you need to install Classic Agents first, and then switch the platform.
|Sensor||Classic Agent||AppMon Agent|
|User Experience sensor|
Check the Agent log file in the AppMon Client: