Monitoring the System
This section points to parameters that are useful for monitoring the health of the Paragon Active Assurance system.
System Parameters
Standard system parameters:
- CPU utilization
- Should stay below 80%
- Memory utilization, excluding cache and buffers
- Should stay below 80%
- Disk utilization
- Should stay below 80%
Application Parameters
For Control Center, run the command
ncc status
The following parameters are of particular interest:
test_agent_appliance_online
: This indicates how many Test Agent Appliances are currently logged in to the server. The desirable numbers here are of course dependent on how you deploy the Test Agents.scheduled_call_latency
: This indicates how far behind schedule the background job processing is. Among other things, this processing collects results from Test Agents and generates periodic reports. The latency should stay below 10 s.
Licenses
The time remaining of the validity period for the license activated on the server can be inspected with the command
ncc license show
In the output from this command, look for the following:
violated_after
: On this date, the license will expire. The system will still work, but a warning will be shown to users.disabled_after
: On this date, the system will be disabled. Users will still be able to access the system to view results and reports, but no new measurements will be collected.
Processes
The following ncc processes should normally be running:
- netrounds-callexecuter
- netrounds-confd
- netrounds-probe-login
- apache2
- openvpn@netrounds
Logs
The file /var/log/apache2/netrounds_error.log
by default contains all logs
from Control Center. The configuration of the logging is done using the Python logging
module configuration schema (https://docs.python.org/2/library/logging.config.html#configuration-dictionary-schema).
Paragon Active Assurance provides two custom formatters that yield additional information about log entries and thus should be favored over Python's default formatters:
- The formatter
netrounds.utils.loggers.ContextFormatter
providesrecord_tags
andcontext_tags
that provide additional information about the context of the log entry, for example what Test Agent the log entry is about. Colors are also supported. - The formatter
netrounds.thirdparty.logstash_formatter.ContextLogstashFormatterV1
outputs a JSON format compatible with Logstash.
The custom formatters are added by default in:
LOGGING['formatters']['context']
LOGGING['formatters']['context_color']
LOGGING['formatters']['logstash']