NDOUtils - Data Processing Options in ndomod.cfg

Overview

The NDOUtils NDOMOD broker module can be configured to only processed certain types of data. This is defined in the ndomod.cfg file. There are two ways of defining this which are explained in this article.

Location of settings

This article explains settings defined in the file ndomod.cfg which can usually be found in the nagios etc directory (/usr/local/nagios/etc/ in Nagios xi).

Editing Files

In many steps of this article you will be required to edit files. This documentation will use the vi text editor. When using the vi
editor:

• To make changes press i on the keyboard first to enter insert mode
• Press Esc to exit insert mode
• When you have finished, save the changes in vi by typing :wq and press Enter

Defined by Bitmask

Originally the different options have been defined by calculating a bitmask and defining this with the option:

data_processing_options=xxxx

Where xxx is the bitmask number.

To calculate the bitmask you would need to 'OR' the values of the following options:

For example, in Nagios xi the bitmask of 67108669 is used which includes all of these options EXCEPT for NDOMOD_PROCESS_TIMED_EVENT_DATA, NDOMOD_PROCESS_HOST_CHECK_DATA and NDOMOD_PROCESS_SERVICE_CHECK_DATA as per:

data_processing_options=67108669

Defined by Individual Options

As of ndoutils2.x, these options can be defined individually instead of using the data_processing_options bitmask. The options are:

NOTE: you must remove the data_processing_options=xxxx setting from ndomod.cfg if you wish to use the options above.

Change from data_processing_options to individual options.

This example shows you how to change from using the data_processing_options to the individual options for a Nagios xi server.

Edit the file /usr/local/nagios/etc/ndomod.cfg.

Comment out the data_processing_options line by adding a # at the beginning of the line:

#data_processing_options=67108669

Now paste the following into the file (after the line you just commented out):

acknowledgement_data=1
adaptive_contact_data=1
adaptive_host_data=1
adaptive_program_data=1
adaptive_service_data=1
aggregated_status_data=1
comment_data=1
contact_status_data=1
downtime_data=1
event_handler_data=1
external_command_data=1
flapping_data=1
host_check_data=0
host_status_data=1
log_data=1
main_config_data=1
notification_data=1
object_config_data=1
process_data=1
program_status_data=1
retention_data=1
service_check_data=0
service_status_data=1
statechange_data=1
system_command_data=1
timed_event_data=0

Save the changes to the file.

You need to restart the nagios service using one of the commands below:

RHEL 6 | CentOS 6 | Oracle Linux 6 | Ubuntu 14

service nagios restart

RHEL 7 | CentOS 7 | Oracle Linux 7 | Debian | Ubuntu 16/18

systemctl restart nagios.service

The NDOUtils NDOMOD broker module is now configured using the individual option instead of the bitmask.

Conclusion

After reading this article you should have a better understanding of how the NDOUtils NDOMOD broker module can be configured for it's data processing options.

Final Thoughts

For any support related questions please visit the Nagios Support Forums at:

http://support.nagios.com/forum/