Use the Monitoring Agent
Several NeoLoad Controllers can use a Monitoring Agent to supervise the network. The number of NeoLoad Controllers can be configured.
Limit the number of Controllers connected to a Monitoring Agent
To limit the number of Controllers connected to a Monitoring Agent, follow these steps:
-
On the Monitoring Agent side, edit the key
[Network]connections.max.controllers
of the file<Monitoring Agent>/conf/monitoringAgent.properties
. -
Set the key with a value standing for the highest number of Controllers allowed. Or leave the default
-1
value for an unlimited number of potential connections. -
Restart the Monitoring Agent.
Limit the number of monitoring sessions on a Monitoring Agent
To limit the number of monitoring sessions on a Monitoring Agent, follow these steps:
-
On the Monitoring Agent side, edit the key
[Network]connections.max.monitorengines
of the file<Monitoring Agent>/conf/monitoringAgent.properties
. -
Set the key with a value standing for the highest number of monitoring sessions. Or leave the default
-1
value for an unlimited number of potential sessions. -
Restart the Monitoring Agent.
Configure the disconnection timeout of a monitoring session
To configure the disconnection timeout of a monitoring session, follow these steps:
-
On the Monitoring Agent side, edit the key
[MonitorEngine]me.no.activity.shutdown.delay
of the file<Monitoring Agent>/conf/monitoringAgent.properties
. -
Set the key with a value standing for the number of seconds before an unused monitoring session stops. Or leave the
14400
default value for a 4-hour timeout. -
Restart the Monitoring Agent.