ITSI module for Nmon Metricator¶

The ITSI module for Nmon Metricator provides rich builtin Key Performance Indicators (KPIs), service templates and ITSI native views for entities health analysis.

Entities import¶

The entities import is an automatic process linked to the following scheduled report:

DA-ITSI-METRICATOR-NMON-OS_Hosts_Search

By default, the entities import process runs every 4 hours and imports in ITSI any entity available using the Nmon configuration data.

After the deployment of the ITSI module, and the deployment of the Technology addons, the entities creation will be achieved automatically without the need of any manual action.

However, the entities import process can be achieved manually at any time:

Configure / Entities / New Entity / Import from search
Choose Module, and search for the ITSI Metricator Nmon module
Any existing entity will be updated, if any update, meaning the process can be run without affecting existing entities
The module relies on the field / value “itsi_role=nmon_host” to identify entities and provide the context relevant health views

Notes: when running manually the import, the time range will be restricted to the last 60 minutes which may not be enough to match the nmon configuration events, select a larger period such as last 7 days.

Service creation / KPIs import¶

Builtin KPIs¶

The ITSI module provides the following builtin Key Performance Indicators (KPIs):

CPU Utilization: % = CPU usage in percentage for all available CPU cores in the system
CPU Wait I/O % = CPU percentage waiting for Input / Output for all available CPU cores in the system
Memory Free: % = Percentage of free memory (for Linux, this excludes buffers and cached memory)
Swap Memory Free: % = Percentage of free swap, if any. (for Linux, this excludes swap cached)
Network packets = Number of network packets (sum for all interfaces but loopback interfaces)
Network traffic (kpbs) = Average network traffic in KBps (average traffic for all interfaces but loopback interfaces)
Storage_busy_time = Percentage of time the storage was busy (average busy time for all available devices)
Storage Free Space: % = Percentage of free space (minimal available free space percentage from all available file systems)
Storage Free Inodes: % = Percentage of inodes free (minimal available free inode percentage from all available file systems)
Storage_IOPS = Average number of IOPS for all available storage devices
Storage read IOPS = Average number of read IOPS for all available storage devices
Storage write IOPS = Average number of write IOPS for all available storage devices
Storage transfer per sec = Transfer per sec in KB/s, average for all available storage devices
Storage read transfer per sec = Read transfer per sec in KB/s, average for all available storage devices
Storage write transfer per sec = Write transfer per sec in KB/s, average for all available storage devices

Notes: This list of KPIs represents the essentials KPIs used to analyse the system performance health, however even more metrics are available in the nmon data, and you can create your own KPI basesearches if required.*

KPIs treshholding:

Network and storage performance related KPIs have no threshold configured and are provided as info metrics
Others KPIs have a default threshold template that can easily be modified up to your needs, for which we recommend creating a custom service template you use to import your KPIs if you need to modify them and apply your own threshold model

Adding the builtin KPIs to services¶

Adding the builtin KPIs to existing or new services:

Good ITSI practices recommend to clone the builtin KPIs into custom version (prefixed with your customer ID), and finally adding add these cloned KPIs to a custom services you will use to import the KPIs in your ITSI services
This is essentially recommended to allow customizing the default OOTB modules for performances purposes, such as restricting the indexes or adding more constraints
This practice is not required with the ITSI module as KPIs searches are already as optimised as possible
If you use a different indexes naming convention than the default Metricator model, ensure to modify the macro “nmon_metrics_index” which is called in every KPI basesearch
If you really need to customize the KPI builtin base searches, then cloning the KPIs is the right way as the ITSI module is read only

Adding the builtin KPIs can be easily achieved by selecting the KPIs from the template service called “NMON OS Performance KPIs”:

Entities filtering is achieved against the field itsi_role=nmon_host which is automatically defined for each discovered entity:

Host health views¶

The OS heath view is automatically available for entities that generating Nmon data by the Technology addons, the view can be acceded from various places such as the ITSI entity health view: