Controller Settings for the Cluster Agent
These properties are recommended for a Controller supporting the Cluster Agent. Certain Server Visibility properties will apply to all instances of Server Visibility and the Cluster Agent.
| Property | Description | Recommended |
|---|---|---|
| sim.cluster.agent.limit | Maximum number of Cluster Agents per account. Configurable at the account level. For example, if you set the sim.cluster.agent.limit to a value of five, and you have ten Cluster Agents reporting, then the Controller randomly selects a subset of Cluster Agents. These random Cluster Agents will not be registered and reported. If the configured limit is reached, any new Cluster Agent will not be registered. | 10 |
| sim.cluster.pod.limit | Maximum number of pods per Cluster Agent per account. Configurable at the account level. If the number of pods exceeds the configured limit, the Cluster Agent randomly selects a set of pods that will not register or report. | 1500 |
| sim.machines.pod.purger.batchSize | The maximum number of pods assigned per thread for purging |
200 |
| sim.machines.pod.purger.maxThreadCount | The maximum number of threads for pod purge |
10 |
| sim.machines.registrations.maxPerSecondPerAccount | Maximum number of machine registrations allowed per account, per second. This property applies to all instances of Server Visibility and the Cluster Agent. | 10000 |
| sim.cluster.container.limit | Controller level limit for the number of containers per cluster. This is used if there is no account-level configuration. To overwrite at account-level, add an additional property to the corresponding account. This property only affects the Cluster Agent. | 3000 |
| sim.machines.offline.toStaleTimeoutMillis | Length of time in milliseconds before an offline machine is considered stale, and eligible for purging. This property applies to all instances of Server Visibility and the Cluster Agent. | 172,800,000 ms (2 days) |
| sim.machines.registrations.update.frequency | Machine's timestamp update frequency in milliseconds. This property applies to all instances of Server Visibility and the Cluster Agent. | 86,400,000 ms (1 day) |
| sim.cluster.events.maxPerMinute | Controller level limit for the number of cluster events that are allowed per minute. This property only affects the Cluster Agent. | 4000 |
| sim.machines.simAllowed |
Availability of Server Visibility features. This property must be set to true to send the data (metrics) from Cluster Agent to Controller. | true |
| sim.cluster.monitoring.enabled | This property enables the Cluster Agent on the Controller. If set to false, all Cluster Agents stop reporting metrics and components, but still register every minute. This property only affects the Cluster Agent. | true |
|
sim.machines.offline.toStalePodTimeoutMillis |
The time duration in milliseconds before the offline pods and containers are considered stale, and eligible for purging. This property applies to all instances of Server Visibility and the Cluster Agent. | 2592000000 ms |
|
sim.machines.deleteStalePods.maxLimit |
The number of stale pods and containers to be considered for deletion. | 5000 |
|
sim.machines.pod.eviction.cronExpression |
To provide the cron expression to run the pod purger. This helps in configuring the frequency of running the purger. | "0 0 0 ? * SUN *" |
See Controller Settings for Server Visibility.
On-Premises Customers
For on-premises customers, to modify the Cluster Agent properties for your account:
-
Log in to the Administration Console with the administrator root password.
- Select Controller Settings.
- In the Controller Settings list, search for the setting.
- In the Value field, enter the recommended value.
- Click Save.
- Log out of the Administrator Console.
SaaS Customers
For SaaS customers, create a customer support ticket to have the Cluster Agent properties updated for your account.