You are hereSupport / Ask The Community / Checking status for remote Longitude agents
Checking status for remote Longitude agents
Longitude can be configured to collect data through an agent installation - this is useful if you need to collect data from devices at a remote site, on the other side of a firewall, or where you would need to use an alternate set of Windows credentials. However, especially for agents at remote sites, there can be a delay in collecting monitored data if the Management Console loses contact with the Longitude agent.
The Consolidator component in the Longitude Management Console will check connectivity with any agents it collects from, and will email a notice if connectivity fails to the MailToForLongitudeProblems address. In order to prevent false alerts, the Consolidator will not alert until there have been multiple connection failures to the agent.
You can use a transaction as an additional check on agent status. Depending on the network between the Management Console and the Agent, you can use Ping (to check the network), Port (to check the statistics server port - default = 7220 TCP), Service (for the Heroix Longitude Statistics Server), or you can create a script to check the agent using your favorite scripting language and use a Windows Script transaction. After setting up the transaction, remember to configure an alert for the agent.