Manager Status - Field Help
Configuration Settings
Edit any of the values on the Manager Status panel and click Update Configuration.
- Sensitivity level
- A number from 0 to 100 to be used as the weight percentage in setting the minimum sensitivity to weights update. This setting defines when the manager should change its weighting for the server based on external information. The default of 5 creates a minimum sensitivity of 5%.
- Smoothing index
- A positive floating point number representing an index that smooths the variations in weight when load balancing. The default value is 1.5.
- Weights refresh cycle
- A positive number representing the number of intervals before querying the executor for a refresh of information about new and active connections. The default value is 2.
- Update interval
- A positive number representing in seconds how often the manager will
update weights of the servers to the executor, updating the criteria that the executor uses to load balance client requests. The default value is 2.
- Reach update interval (seconds)
- A positive number representing the number of seconds between attempts to
reach targets in the configuration. The default value is 7.
Note: This does not apply to CBR.
- Manager logging level
- The level at which the manager logs its activities: none - 0, minimal - 1,
basic - 2, moderate - 3, advanced - 4, verbose - 5. The default is minimal.
- Maximum manager log size
- A maximum number of bytes to be logged in the manager log file. The default value is 1 MB.
- Reach logging level
- The level at which the manager logs the Reach activities: none - 0, minimal - 1,
basic - 2, moderate - 3, advanced - 4, verbose - 5. The default is minimal.
Note: This does not apply to CBR.
- Maximum reach log size (bytes)
- An integer representing the maximum number of bytes that will be logged by the
reach advisor. The default value is 1 MB.
Note: This does not apply to CBR.
- Binary logging interval (seconds)
- The interval, in seconds, of how often information is written to the binary logs.
The binary logging feature allows server information to be stored in binary log files for each server
defined in the configuration.
The manager sends server information to the log server every manager
interval. The information is written to the logs only if the specified
log interval seconds have elapsed since the last record was written to the
log. Default binary logging interval is 60. The following information
is stored in the binary log for each server:
- cluster address
- port number
- server address
- server weight
- server total connections
- server active connections
- server port load
- server system load
Note: There is some interaction between the settings of the manager
interval and the log interval. Since the log server is provided with
information no faster than manager interval seconds, setting the log
interval less than the manager interval effectively sets it to the same as the
manager interval.
- Binary Log Retention (hours)
- The amount of time, in hours, log files are kept. Log files older than the retention
hours specified will be overwritten. The default value is 24.
-
Current Statistics
- Metric port
- The number of the port on which a system-monitoring program, such as Metric Server, will
report system loads. The default value is 10004 for Dispatcher,
Mailbox Locator and Site Selector and 10003 for CBR.
- Log filename
- The name of the manager log file.
- Binary logging
- Status for binary log setting.
- List of Advisors
- The currently active advisor names and their port numbers and/or clusters are listed.
To remove an advisor, highlight the advisor in the list and click remove.
|