Custom plugins

Overview

OP5 Monitor has an open architecture. You can extend the standard functionality by adding custom plugins from the Naemon community or developed by your own organisation.

The sections below explain how to create and install custom plugins. ITRS does not provide any support for custom plugins.

Macros

Custom plugins in OP5 Monitor rely on the use of Naemon macros. For more information, see Macros in Manage commands.

Create a custom plugin

The following procedure explains how to write a simple shell script to run as a plugin. You can use it as a basis for creating more complex custom plugins of your own.

To create a custom plugin:

1. Log on to the OP5 Monitor server, using SSH.
2. Add your custom plugin to directory /opt/plugins/custom and make it executable. In the following example, we are adding a new file called check_local_helloworld:

cd /opt/plugins/custom 
touch check_local_helloworld
chmod 755 check_local_helloworld

3. You can now edit your plugin file to add some checking logic. In the following example, we add code to print a value:

#!/bin/sh 
echo 'WARNING: Hello, world!'
exit 1

4. You can now execute the file to test it:

$ ./check_local_helloworld
WARNING: Hello, world! 
$ echo $?
1									

Success: You have created your custom plugin. The next step is to install it in OP5 Monitor.

Install custom plugins on a standard OP5 Monitor server

You install a custom plugin by creating a new command for it and adding the command to a service configuration.

To install a custom plugin:

1. In the OP5 Monitor interface, click Manage > Configure > Commands.
2. Enter the details of the new command. For the plugin created in Create a custom plugin, the parameters are as follows:

command_name: check_local_helloworld 
command_line: $USER1$/custom/check_local_helloworld

For guidance on creating commands, see Create and update commands in Manage commands.

3. Add the command to a service configuration. For guidance, see Configure a service in Manage hosts and services. You can now see it in the service list views:

Install custom plugins on a Slim Poller

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
FROM op5com/slim-poller_naemon-core# Run as root while installingUSER rootARG PLUGIN_PATH=/opt/plugins/customWORKDIR /tmp# Make sure the custom plugins path existsRUN mkdir -p $PLUGIN_PATH# Install dependenciesRUN yum install -y ruby rubygems rubygem-json# install gitRUN yum install -y git# Checkout the sourcecode from gitRUN git clone https://github.com/xorpaul/check_puppetdb.gitRUN cp ./check_puppetdb/check_puppetdb.rb $PLUGIN_PATH#clean upRUN rm -rf ./check_puppetdb/# Change back to correct monitor userUSER $MON_UID

docker build -f <path/to/dockerfile>	

docker pull op5com/slim-poller_naemon-core
docker build . --no-cache			

Example custom plugin

The following example creates a plugin to print the OP5 Monitor storage path:

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
#!/bin/bash# Create a function to print the storage pathstoragepath() {  grep ^storagepath /etc/op5-backup/main.conf |tail -1 |sed 's/^[^"]*"//g' | sed 's/"$//g'}# Put the storage path in an environmental variableSTORAGEPATH=`storagepath`# Test if the storagepath exists and is a directoryif [[ ! -d "$STORAGEPATH" ]]; then  # Print a warning message for the web gui  echo "op5-backup is not properly configured for local operation"  # Exit with status Warning (exit code 1)  exit 1fi# If the script reaches this point then the test passed# Print an OK messageecho $STORAGEPATH exists# Exit with status OKexit 0

For more information on custom plugins, see Naemon - Plugin API documentation.