System

• Pro.Monior allows administrators to fully configure a system with an specific functionality : System.
• This feature is subdivided in the following sections (see image below) :

In this section, administrators can configure :

• How many parallel tasks a monitoring process will execute :
  • This setting will determine how many single taks (monitors) Redpeaks is able to execute at the same time
  • Notive that this setting is tight to the number of microprocessors (cores) of the machine on which Redpeaks has been installed
• The allocation (in GB) of the monitoring processes memory :
  • This value concerns the maximum amount of memory that can be allocated to an entire monitoring batch (to be seen as a container of monitors)
• Monitoring processes' timeout (in minutes)
• The possibility to compress or not monitoring results. Notice that compressing results will demand a certain CPU process time
• Use Tomcat Proxy : The possibility to have monitoring processes use the same proxy settings as tomcat
  • When Use Tomcat proxy for monitoring processes is active, the monitoring processes (workers) reuse the proxy configured for the central server
  • Notice that monitoring processes run in a separate process and do not inherit the proxy automatically, so this option is needed when the network requires a proxy

Under this section, administrators are able to :

• Activate monitors result retention:
  • To store monitor execution results.
  • This function is useful to track generated alarms and metrics, long run times or aborted results
• Store statistics only:
  • Keep only track of monitor execution status (won't store alarms/metrics/results).
  • This will store much less data in the DB.
• Set the minimum number of seconds a given job (Redpeaks Monitor) executes its task before storing the job result.
  • This setting is particularly useful when Administrator need to track monitors that have taken a long time to execute.
• Set the number of days that Redpeaks will keep in memory the monitoring data
• Set the number of days that Redpeaks will store in memory monitor tests information
• Set the number of days to keep all generated reports
• Set the number of reports to remove per execution of cleanup procedure.
• Configure the number of days Redpeaks log files will be kept in memory - at disposal for downloading -
• Activate statistics metrics:
  • Store execution statistics metrics for the monitors
  • This is useful to follow run times and execution trends over time
• Store aborted monitor results only:
  • Keep only the results of monitors that were aborted
  • This stores much less data and helps focusing on aborted executions
• Set the number of days that Redpeaks will keep the change tracking entries (default 90 days)
• Set the maximum number of configuration snapshots that Redpeaks will keep (default 50) - older snapshots are removed when this limit is reached
• Launch a “clean up procedure” that will immediately delete all retention data prior to the settings above explained

• When Activate telnet check is active, the connector check will first try to reach the host and port defined in connectors.
• This helps clearing out routing and firewall issues quicker.
• You can also define the telnet timeout
• Note: Agents will inherit from central server telnet configuration when running as non local scheduler

• Whenever a Redpeaks user performs an action that will provoke a significant change in the system, administrators can give the possibility or not - checking on “Optional” - to a user to enter a note concerning the reason for that action, or make this feature mandatory - checking on “Mandatory” -. Check “Deactivated” option to immediately deactivate this function.

In this section, administrators will be able to :

• Set the timeout value (in seconds) for a report to be generated

Under this section, the administrator can determine :

• When a given system is to be considered as a “flapping system” trough the following parameters :
  • Period : It represents the time lapse (in hours) to be taken into account
  • Threshold : It represents the system flaps threshold, once this value is overreached (within the Period parameter value), the system will be considered as “flapping system”
• A Clear flapping data button is available to immediately remove the stored flapping history of the connectors

In this section, administrators are able to :

• Allow duplicate short name
  • When this option is active, two monitors can share the same short name, when deactivated, Redpeaks forces each monitor short name to be unique