Manager Status - Field Help
Current Statistics
- Metric port
- The number of the port on which a system-monitoring program, such as Metric Server,
reports system loads. The default value is 10004 for Dispatcher.
- Log file name
- The name of the manager log file.
- Binary logging
- Status for binary log setting.
Configuration Settings
Edit any of the values on the Configuration Settings tab, then click Update Configuration.
- Sensitivity level
- A number from 1 to 100 used as the weight percentage to set 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 that occur before the executor is queried
for a refresh of information about new and active connections. The default value is 2.
- Update interval (seconds)
- A positive number representing, in seconds, how often the manager updates weights of the servers
to the executor. The manager updates 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.
- Manager logging level
- The level at which the manager logs its activities. The range is None to Verbose, with None
meaning nothing is logged and Verbose meaning everything is logged. The default is Minimal. Select from
the following values:
- None
- Minimal
- Basic
- Moderate
- Advanced
- Verbose
- Maximum manager log size (bytes)
- Sets the maximum size of the manager log. When you set a maximum size for
the log, the file wraps; when the file reaches the specified size, the subsequent entries are written
from the top of the file, overwriting the previous log entries. This log size cannot be set smaller than
the current size of the log. Log entries are time-stamped to display the order in which they were
written. The higher you set the log level, the more carefully you must choose the log size, because you
can quickly run out of space when logging at the higher levels.
You can specify a positive number greater than zero, or up to 1 MB. The log file
may not reach the exact maximum size before overwriting, because the log entries vary
in size. Choose Unlimited or enter the number of bytes. The default value is 1048576 bytes.
- Reach logging level
- The level at which the manager logs the Reach activities. The range is None to Verbose, with
None meaning nothing is logged and Verbose meaning everything is logged. The default is Minimal.
Select from the following values:
- None
- Minimal
- Basic
- Moderate
- Advanced
- Verbose
- Maximum reach log size (bytes)
- An integer representing the maximum number of bytes that will be logged by the
reach advisor. Choose Unlimited or enter the number of bytes. The default value is 1048576 bytes.
- Metric logging level
- The level at which the metric logs its activities. The range is None to Verbose, with
None meaning nothing is logged and Verbose meaning everything is logged. The default is Minimal.
Select from the following values:
- None
- Minimal
- Basic
- Moderate
- Advanced
- Verbose
- Maximum metric log size
- Represents the maximum number of bytes that will be logged by the metric. Choose
Unlimited or enter the number of bytes. The default value is 1048576 bytes
- Binary logging interval (seconds)
- How often, in seconds, 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 information is provided to the log server faster than
the manager interval, 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 are overwritten. The default value is 24.
-
- List of Advisors
- A list of currently-active advisor names, their port numbers and/or clusters.
To remove an advisor, highlight the advisor in the list, then click Remove.
|