The Component extension provides a generic database storage mechanism for discovery and poller modules. The Driver behind this extension was to provide the features of ports, in a generic manner to discovery/poller modules.
It provides a status (Nagios convention), the ability to Disable (do not poll), or Ignore (do not Alert).
The database structure contains the component table:
mysql> select * from component limit 1; +----+-----------+------+------------+--------+----------+--------+-------+ | id | device_id | type | label | status | disabled | ignore | error | +----+-----------+------+------------+--------+----------+--------+-------+ | 9 | 1 | TEST | TEST LABEL | 0 | 1 | 1 | | +----+-----------+------+------------+--------+----------+--------+-------+ 1 row in set (0.00 sec)
These fields are described below:
id- ID for each component, unique index
device_id- device_id from the devices table
type- name from the component_type table
label- Display label for the component
status- The status of the component, retrieved from the device
disabled- Should this component be polled?
ignore- Should this component be alerted on
error- Error message if in Alert state
The component_prefs table holds custom data in an Attribute/Value format:
mysql> select * from component_prefs limit 1; +----+-----------+-----------+-----------+ | id | component | attribute | value | +----+-----------+-----------+-----------+ | 4 | 9 | TEST_ATTR | TEST_ATTR | +----+-----------+-----------+-----------+ 2 rows in set (0.00 sec)
When this data from both the
component_prefs tables is returned in one single consolidated array, there is the potential for someone to attempt to set an attribute (in the
component_prefs) table that is used in the
component table. Because of this all fields of the
component table are reserved, they cannot be used as custom attributes, if you update these the module will attempt to write them to the
component table, not the
Create an instance of the component class:
$COMPONENT = new LibreNMS\Component();
Now you can retrieve an array of the available components:
$ARRAY = $COMPONENT->getComponents($DEVICE_ID, $OPTIONS);
getComponents takes 2 arguments:
DEVICE_IDor null for all devices.
OPTIONS- an array of various options.
getComponents will return an array containing components in the following format:
Array ( [X] => Array ( [Y1] => Array ( [device_id] => 1 [TEST_ATTR] => TEST_ATTR [type] => TEST [label] => TEST LABEL [status] => 0 [ignore] => 1 [disabled] => 1 [error] => ), [Y2] => Array ( [device_id] => 1 [TEST_ATTR] => TEST_ATTR [type] => TESTING [label] => TEST LABEL [status] => 0 [ignore] => 1 [disabled] => 0 [error] => ), ) )
Where X is the Device ID and Y1/Y2 is the Component ID. In the example above,
TEST_ATTR is a custom field, the rest are reserved fields.
Options can be supplied to
getComponents to influence which and how components are returned.
You can filter on any of the reserved fields. Filters are created in the following format:
$options['filter']['FIELD'] = array ('OPERATOR', 'CRITERIA');
FIELD- The reserved field to filter on
OPERATOR- 'LIKE' or '=', are we checking if the FIELD equals or contains the CRITERIA.
CRITERIA- The criteria to search on
There are 2 filtering shortcuts:
$DEVICE_ID is a synonym for:
$OPTIONS['filter']['device_id'] = array ('=', $DEVICE_ID);
$OPTIONS['type'] = $TYPE is a synonym for:
$OPTIONS['filter']['type'] = array ('=', $TYPE);
You can sort the records that are returned by specifying the following option:
$OPTIONS['sort'][FIELD] = 'DIRECTION';
Where Direction is one of:
ASC- Ascending, from Low to High
DESC- Descending, from High to Low
To create a new component, run the
$ARRAY = $COMPONENT->createComponent($DEVICE_ID, $TYPE);
createComponent takes 2 arguments:
DEVICE_ID- The ID of the device to attach the component to.
TYPE- The unique type for your module.
This will return a new, empty array with a component ID and Type set, all other fields will be set to defaults.
Array (  => Array ( [type] => TESTING [label] => [status] => 1 [ignore] => 0 [disabled] => 0 [error] => ) )
When a component is no longer needed, it can be deleted.
This will return
True on success or
False on failure.
To edit a component, the procedure is:
Edit the Array
Once you have a component array from
getComponents the first thing to do is extract the components for only the single device you are editing. This is required because the
setComponentPrefs function only saves a single device at a time.
$ARRAY = $COMPONENT->getComponents($DEVICE_ID, $OPTIONS); $ARRAY = $ARRAY[$DEVICE_ID];
Then simply edit this array to suit your needs. If you need to add a new Attribute/Value pair you can:
$ARRAY[COMPONENT_ID]['New Attribute'] = "Value";
If you need to delete a previously set Attribute/Value pair you can:
If you need to edit a previously set Attribute/Value pair you can:
$ARRAY[COMPONENT_ID]['Existing Attribute'] = "New Value";
Write the components
To write component changes back to the database simply:
When writing the component array there are several caveats to be aware of, these are:
$ARRAYmust be in the format of a single device ID -
$ARRAY[$COMPONENT_ID][Attribute] = 'Value';NOT in the multi device format returned by
$ARRAY[$DEVICE_ID][$COMPONENT_ID][Attribute] = 'Value';
- You cannot edit the Component ID or the Device ID
- reserved fields can not be removed
- if a change is found an entry will be written to the eventlog.
Component details are available via the API. Please see the API-Docs for details.
It is intended that discovery/poller modules will detect the status of a component during the polling cycle. Status is logged using the Nagios convention for status codes, where:
0 = Ok, 1 = Warning, 2 = Critical
If you are creating a poller module which can detect a fault condition simply set STATUS to something other than 0 and ERROR to a message that indicates the problem.
To actually raise an alert, the user will need to create an alert rule. To assist with this several Alerting Macro's have been created:
%macro.component_normal- A component that is not disabled or ignored and in a Normal state.
%macro.component_warning- A component that is not disabled or ignored and NOT in a Warning state.
%macro.component_critical- A component that is not disabled or ignored and NOT in a Critical state.
To raise alerts for components, the following rules could be created:
%macros.component_critical = "1"- To alert on all Critical components
%macros.component_critical = "1" && %component.type = "<Type of Component>"- To alert on all Critical components of a particular type.
If there is a particular component you would like excluded from alerting, simply set the ignore field to 1.
The data that is written to each alert when it is raised is in the following format:
COMPONENT_TYPE - LABEL - ERROR
To see an example of how the component module can used, please see the following modules:
- Cisco CBQoS
- Cisco OTV