Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from this space and version 8.1.0

...

These are OID numbers from which SNMP clients can gather information. They are directly provided by the OS:


CPU Load time:
1 minute Load: .1.3.6.1.4.1.2021.10.1.3.1
5 minute Load: .1.3.6.1.4.1.2021.10.1.3.2
15 minute Load: .1.3.6.1.4.1.2021.10.1.3.3

Memory:
Total memory:
.1.3.6.1.4.1.2021.4.5.0

Memory Free:
.1.3.6.1.4.1.2021.4.6.0

Disks:
Path where the disk is mounted: 
.1.3.6.1.4.1.2021.9.1.2.1


Path of the device for the partition: 
.1.3.6.1.4.1.2021.9.1.3.1


Total size of the disk/partion (kBytes): 
.1.3.6.1.4.1.2021.9.1.6.1


Available space on the disk: 
.1.3.6.1.4.1.2021.9.1.7.1


Used space on the disk: 
.1.3.6.1.4.1.2021.9.1.8.1


Percentage of space used on disk: 
.1.3.6.1.4.1.2021.9.1.9.1


Percentage of inodes used on disk: 
.1.3.6.1.4.1.2021.9.1.10.1

Network:
Network interfaces:
.1.3.6.1.2.1.31.1.1.1.1

Network Received Packets:
.1.3.6.1.2.1.31.1.1.1.7.1

Network Outgoing Packets:
.1.3.6.1.2.1.31.1.1.1.11.2

Individual counters for incoming traffic in bytes:
.1.3.6.1.2.1.31.1.1.1.6

Individual counters for outgoing traffic in bytes:
.1.3.6.1.2.1.31.1.1.1.10

The number of inbound packets that contained errors
.1.3.6.1.2.1.2.2.1.14

Current maximum allowed connections (ProvisionStats.maxConnections)
.1.3.6.1.4.1.36009.4.0

The peak number of connections since the database server daemon was started (ProvisionStats.maxUsedConnections)
.1.3.6.1.4.1.36009.4.1

The number of currently open connections (ProvisionStats.threadsConnected)
.1.3.6.1.4.1.36009.4.2


Note

NOTE: If the MySQL maximum connections limit is reached, then ProVision will not be able to respond to the SNMP Daemon, as it will not be able to connect to MySQL. Please keep this in mind when setting alert thresholds.

NOTE: ProVision collects information from /proc/meminfo. We calculate usedMemory in the following way: 100 - ((availableMemory / totalMemory) * 100). 



Info

ProVision SNMP KPIs can be configured to send trap events for the ProVision application. For the host system KPIs (CPU, RAM, etc.) the monitoring tool will need to be configured to poll the KPIs and then set the alert thresholds accordingly.


Expand
titleConfiguration Tips

Open data/globals.php and add the following lines.

SNMP Version 2c:

define('SNMP_TRAP_VERSION', 'v2c');
define('SNMP_TRAP_V2C_COMMUNITY', 'enter_v2c_community');
define('SNMP_TRAP_HOST', 'enter_snmp_host');

SNMP Version 3:

define('SNMP_TRAP_VERSION', '3');
define('SNMP_TRAP_V3_ENGINE_ID', 'enter_engine_id');
define('SNMP_TRAP_V3_AUTH_USER', 'enter_auth_user');
define('SNMP_TRAP_V3_AUTH_PASSWORD', 'enter_auth_password');
define('SNMP_TRAP_V3_AUTH_PROTOCOL', 'enter_auth_protocol');
define('SNMP_TRAP_V3_PRIV_PASSWORD', 'enter_auth_priv_password');
define('SNMP_TRAP_HOST', 'enter_snmp_host');


SNMP TrapsV3 using AES cypher:

define('SNMP_TRAP_VERSION', '3');
define('SNMP_TRAP_HOST', '[host]');
define('SNMP_TRAP_V3_ENGINE_ID', '[engine_id]');
define('SNMP_TRAP_V3_AUTH_USER', '[auth_user]');
define('SNMP_TRAP_V3_AUTH_PASSWORD', '[auth_password]');
define('SNMP_TRAP_V3_PRIV_PASSWORD', '[passphrase]');


...