Sensor State Support

Introduction

In this section we are briefly going to walk through, what it takes to write sensor state support. We will also briefly get around the concepts of the current sensor state monitoring.

Logic

For sensor state monitoring, we have 4 DB tables we need to concentrate about. - sensors - state_indexes - state_translations - sensors_to_state_indexes

We will just briefly tie a comment to each one of them.

Sensors

Each time a sensor needs to be polled, the system needs to know which sensor is it that it need to poll, at what oid is this sensor located and what class the sensor is etc. This information is fetched from the sensors table.

state_indexes

Is where we keep track of which state sensors we monitor.

state_translations

Is where we map the possible returned state sensor values to a generic LibreNMS value, in order to make displaying and alerting more generic. We also map these values to the actual state sensor(state_index) where these values are actually returned from.

The LibreNMS generic states are derived from Nagios:

0 = OK
1 = Warning
2 = Critical
3 = Unknown

sensors_to_state_indexes

Is as you might have guessed, where the sensor_id is mapped to a state_index_id.

Example

For YAML based state discovery:

mib: NETBOTZV2-MIB
modules:
    sensors:
        state:
            data:
                -
                    oid: dryContactSensorTable
                    value: dryContactSensorValue
                    num_oid: .1.3.6.1.4.1.5528.100.4.2.1.1.2.
                    descr: dryContactSensorLabel
                    index: 'dryContactSensor.{{ $index }}'
                    state_name: dryContactSensor
                    states:
                        - { value: -1, generic: 3, graph: 0, descr: 'null' }
                        - { value:  0, generic: 0, graph: 0, descr: open }
                        - { value:  1, generic: 2, graph: 0, descr: closed }
                -
                    oid: doorSwitchSensorTable
                    value: doorSwitchSensorValue
                    num_oid: .1.3.6.1.4.1.5528.100.4.2.2.1.2.
                    descr: doorSwitchSensorLabel
                    index: 'doorSwitchSensor.{{ $index }}'
                    state_name: doorSwitchSensor
                    states:
                        - { value: -1, generic: 3, graph: 0, descr: 'null' }
                        - { value:  0, generic: 0, graph: 0, descr: open }
                        - { value:  1, generic: 2, graph: 0, descr: closed }
                -
                    oid: cameraMotionSensorTable
                    value: cameraMotionSensorValue
                    num_oid: .1.3.6.1.4.1.5528.100.4.2.3.1.2.
                    descr: cameraMotionSensorLabel
                    index: 'cameraMotionSensor.{{ $index }}'
                    state_name: cameraMotionSensor
                    states:
                        - { value: -1, generic: 3, graph: 0, descr: 'null' }
                        - { value:  0, generic: 0, graph: 0, descr: noMotion }
                        - { value:  1, generic: 2, graph: 0, descr: motionDetected }
                -
                    oid: otherStateSensorTable
                    value: otherStateSensorErrorStatus
                    num_oid: .1.3.6.1.4.1.5528.100.4.2.10.1.3.
                    descr: otherStateSensorLabel
                    index: '{{ $index }}'
                    state_name: otherStateSensorErrorStatus
                    states:
                        - { value: 0, generic: 0, graph: 0, descr: normal }
                        - { value: 1, generic: 1, graph: 0, descr: info }
                        - { value: 2, generic: 1, graph: 0, descr: warning }
                        - { value: 3, generic: 2, graph: 0, descr: error }
                        - { value: 4, generic: 2, graph: 0, descr: critical }
                        - { value: 5, generic: 2, graph: 0, descr: failure }

Advanced Example

For advanced state discovery:

This example will be based on a Cisco power supply sensor and is all it takes to have sensor state support for Cisco power supplys in Cisco switches. The file should be located in /includes/discovery/sensors/state/cisco.inc.php.

<?php

$oids = snmpwalk_group($device, 'ciscoEnvMonSupplyStatusTable', 'CISCO-ENVMON-MIB');

if (!empty($oids)) {
    //Create State Index
    $state_name = 'ciscoEnvMonSupplyState';
    $states = array(
         array('value' => 1, 'generic' => 0, 'graph' => 0, 'descr' => 'normal'),
         array('value' => 2, 'generic' => 1, 'graph' => 0, 'descr' => 'warning'),
         array('value' => 3, 'generic' => 2, 'graph' => 0, 'descr' => 'critical'),
         array('value' => 4, 'generic' => 3, 'graph' => 0, 'descr' => 'shutdown'),
         array('value' => 5, 'generic' => 3, 'graph' => 0, 'descr' => 'notPresent'),
         array('value' => 6, 'generic' => 2, 'graph' => 0, 'descr' => 'notFunctioning'),
     );
    create_state_index($state_name, $states);

    $num_oid = '.1.3.6.1.4.1.9.9.13.1.5.1.3.';
    foreach ($oids as $index => $entry) {
        //Discover Sensors
        discover_sensor($valid['sensor'], 'state', $device, $num_oid.$index, $index, $state_name, $entry['ciscoEnvMonSupplyStatusDescr'], '1', '1', null, null, null, null, $entry['ciscoEnvMonSupplyState'], 'snmp', $index);

        //Create Sensor To State Index
        create_sensor_to_state_index($device, $state_name, $index);
    }
}