This page explains how to create Nacoma save hooks. It is for a technical audience with a good knowledge of scripting.
OP5 Monitor is delivered with a default set of Nacoma save hooks in directory
/opt/monitor/op5/nacoma/hooks/save, which are triggered every time a user saves a configuration from Manage > Configure in OP5 Monitor. You can create your own custom save hooks in the same directory, allowing you to perform environment-specific operations whenever users save data in OP5 Monitor.
OP5 Monitor executes save hooks every time configuration files are flushed from the database and Nagios has verified them. Hook arguments are as follows:
- The first argument is the user name of the person clicking the Save button.
- The second argument is the full name of the person, retrieved by matching the user name to an OP5 Monitor contact_name. If no matching contact is found, the second argument is a null string.
The hooks receive as input the changelog entries accumulated since the user last imported the configuration files (undo) or flushed them from the database to files (save).
The hooks are run as follows:
- By the web server when a Save command is issued from the user interface.
- As the console user when a Save command is issued by the cli tools.
To create your own save hook, place a script in directory
/opt/monitor/op5/nacoma/hooks/save. We recommend you use Python as your scripting language, although other scripting languages are also possible.
You can use any of the scripts in the same directory as a basis for creating your own. The existing scripts use library
Useful functions and attributes you can use in your scripts are summarised in the following tables. See Example script for more details.
||True if the object was created.|
||True if the object was deleted.|
||True if the object was renamed.|
||ID in the object database before the logged action was applied (a deleted object still has an object ID).|
||Naemon name of the object before the action (null for a created object).|
||Naemon name of the object after the action (null for a deleted object).|
||Username of the user who made the change.|
||Time of the change.|
||PHP serialised representation of the object before the change (null for a created object).|
||PHP serialised representation of the object after the change (null for a deleted object).|
The following example script prints to the Nachos log.
#!/usr/bin/env python2 import sys from nacoma.hooks import Change # Using print here will send the information to the logs def main(): for line in sys.stdin: change = Change(line) # Useful functions if change.is_deleted(): print("Deleted") if change.is_new(): print("New") if change.is_renamed(): print("Renamed") # Useful attributes print(change.type) print(change.id) print(change.oldname) print(change.newname) print(change.username) print(change.time) print(change.pre) print(change.post) if __name__ == '__main__': main()