[Index]
A sysadmin administrator can access the System Monitoring menu (menu model: data/SystemMonitoringConfig) to manage:
Default values are set in an instance called Global.
Alerts
From the Alerts tab on the Configuration menu, the following settings and options can be managed:
Database Size Threshold (GB): the default size is 200 GB
Database Index Size Threshold (GB): the default size is 50 GB
Database Queue Size Threshold: the default size is 500
Transaction Failures to Alert: errors for operations on model types.
The default operation is all Import operations on all data models (data/*)
For the configured alerts, SNMP traps are generated upon failue of the transaction. Refer to the System Monitoring SNMP topic in the Platform Guide for details and examples of the traps.
Metrics Collection
The Metric Collection tab shows:
A configurable RIS API data collector interval which is the time interval that the real-time information (RIS) data collector service polls the Unified CM to obtain the latest phone registration status information for phone instances stored in in the VOSS-4-UC database.
The value is in seconds and the default interval is: 43200 seconds (12 hours)
Important
The status of the collector service can be checked with the the platform CLI app status command - seen as voss-risapi_collector in the example console output snippet below:
platform@VOSS:~$ app status selfservice v19.1.1 (2019-04-04 14:35) |-node running voss-deviceapi v19.1.1 (2019-04-04 14:36) |-voss-cnf_collector running |-voss-queue running |-voss-risapi_collector running |-voss-wsgi running ...
Refer to the Best Practices Guide for further information if this interval needs to be modified.
The RIS data collector service updates the current registration status and/or IP address from the Unified CM Registration Status and IP address at the specified interval - for all clusters in the system.
The Phones list view show Registration Status and IP Address columns containing this data.
The collector service data is then available at the interval from VOSS-4-UC data, instead of a remote fetch of data when showing the list view for phones.
Important
There is also a Activate Phone Status Service option in data/Settings that will fetch the Registration Status of a list of phones when the status action is carried out - see: Activate Phone Status Service.
This does not require that the real-time information (RIS) data collector service be enabled to run at the regular interval.
There is also a macro function get_phone_status available to return this Phone data, given the PKID of the phone. For example:
{{fn.get_phone_status 5ca2b90bce894e0014d488fb}}
Configuration for various system monitoring settings and thresholds for alert generation.
Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||
Alerts | Configuration for various alert generation conditions. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Database | Stores thresholds for database metrics |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Database Size Threshold (GB) | The threshold at which DB size (in gigabytes) starts generating notifications. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Database Index Size Threshold (GB) | The threshold at which DB index size (in gigabytes) starts generating notifications. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Transactions | Specifies configuration for alert generation on transactions. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Transaction Queue Size Threshold | The threshold at which transaction queue size starts generating notifications. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
On Failure | List of transactions for which an alert must be sent on failure. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Entity Type | Type of an entity for which an alert is required such as model, view, or tool. Wildcards are permitted e.g. data/* applies to all data models. Specific types take precedence over wildcards |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Operations | The operations for which alerts are required |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Metric Configuration | Stores settings for configurable metrics |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Resource Count by Hierarchy | Settings for Resource Count by Hierarchy metric. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Model Types | List of model types that are to be aggregated by hierarchy. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Model Type | Name of a model type e.g. data/User |
|
|||||||||||||||||||||||||||||||||||||||||||||||
RIS API data collector interval | Interval in seconds between attempts to run the RIS API data collector |
|
|||||||||||||||||||||||||||||||||||||||||||||||
RIS API excluded device types | Devices to ignore in RIS API responses |
|
|||||||||||||||||||||||||||||||||||||||||||||||
Monitor external devices | Enable monitoring of connectivity to external devices e.g. UC apps |
|