The FSO (Full Stack Observability) Agent is a lightweight component that runs on target hosts to collect system-level metrics, application performance data, and log information. It supports Windows and Linux environments and securely transmits collected data to Applications Manager for processing, visualization, and analysis. Installing the FSO Agent enables detailed, real-time monitoring with minimal overhead and reduced dependency on remote polling.
Note: The information on this page only applies to Applications Manager build 182900 and later . For builds earlier than 182900, refer here.
Browse the following topics to install the FSO agent on various environments:
Ensure the following requirements are met before proceeding with the agent installation:
In addition, ensure that the requirements listed on this page are also met before proceeding to install the FSO agent.
Applications Manager generates an install command that already contains your license key and the server address. Run this command on the target server to install the agent. After the command runs, the server is added to Applications Manager as a monitor automatically.
Navigate to New Monitor -> FSO Agent. The wizard has three steps: Select Platform, Agent Bundle & Capabilities, and Install Agent.
Select the operating system of the target server (Windows or Linux) and click Next.

Note: This is an optional step. By default, Full-Stack Monitoring is enabled. To change the agent bundle or the capabilities, click Edit next to Agent Bundle & Capabilities.

This section shows the agent bundle that Applications Manager uses to install agents, and provides the following options:
Upload new bundle: Allows you to upload a newer agent bundle, as described below.
Caution: Uploading a new bundle replaces the existing FSO agent binaries on the Applications Manager server. Agents that you deploy or upgrade from then use the new bundle.
The Advanced Settings section lists the supported capabilities: Server Monitoring (always enabled), AppLogs, and APM Insight. Clear the checkbox for any optional capability that you do not need. For more information about the capabilities, refer to Agent monitoring.
Copy the command shown on the page and run it on the target server (the server that needs to be monitored).
Important: Always copy the command from the Install Agent step. The command contains your license key and registration ID, so treat it as confidential.

Note: Check the Applications Manager address. The info bar shows the address that the agent will connect to, for example https://<apm-server-host>:10102. If the target server needs a different address, such as a host name, IP address, or NAT or proxy address, click Edit, change the Host or Port, and click Save. Saving regenerates the command.
sudo in a shell.Wait for the agent to register. The wizard shows Waiting for the command to run on the target server with a timer. Keep the page open, as it updates automatically when the agent connects. The progress moves through Execution, Installation, and Installation Complete. When the agent registers, the wizard shows Agent onboarded successfully.

The agent usually registers within a minute after the command finishes. If no agent has registered after about five minutes, the wizard shows No agent has reported yet. In this case:
Open the View Agents tab. The new server appears in the list, and its status changes to Active once the agent is connected and sending data. For details on agent statuses and management capabilities, refer to Manage FSO agents. To view agent details, configure AppLogs and APM Insight, or check agent health, refer to FSO Agent Configuration.

Browse the following links to install FSO agents on multiple servers and hosts for the respective OS:
Once the installation is complete, you can start, stop, or restart the FSO agent for the respective OS using any one of the following methods:
Note: You can start, stop, or restart the agent from the Applications Manager console, on the FSO Agent Configuration page. Use the steps below only when there is a communication issue between the agent server and the Applications Manager server. In that case, start or stop the agent directly on the target server.
Execute the following commands in the command terminal based on the user type and directory location:
# FOR AGENT INSTALLATION VIA ROOT USER#1 For starting the Linux Agent/opt/applicationsmanager/monagent/bin/monagent start#2 For stopping the Linux Agent/opt/applicationsmanager/monagent/bin/monagent stop#3 For restarting the Linux Agent/opt/applicationsmanager/monagent/bin/monagent restart#4 For checking the status of Linux Agent/opt/applicationsmanager/monagent/bin/monagent status# FOR AGENT INSTALLATION IN CUSTOM PATH#1 For starting the Linux Agent[custom_path]/monagent/bin/monagent start#2 For stopping the Linux Agent[custom_path]/monagent/bin/monagent stop#3 For restarting the Linux Agent[custom_path]/monagent/bin/monagent restart#4 For checking the status of Linux Agent[custom_path]/monagent/bin/monagent status It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.
Reviewer Role: Research and Development