solibbs.blogg.se

• #Intermapper probe group code

This will result in probes/plugins that work for both InterMapper and Nagios. If you wish to develop your own command-line probes, we recommend you follow You will have to download the Nagios plugins and build/compile

Many vendors and individuals have created their own InterMapper's command-line probes are similar to Nagios® The total amount of data that can be returned by the program, including return code, reason string, and additional values, is 64k. Script's standard output file is used as the device's reason string, and appears in the status window.

#Intermapper probe group code

InterMapper sets the device's status based on the return code from the

section to invoke the program or script and pass arguments to it. The (Pg 1) section - controls what appears in the device's Status window. The (Pg 1) section - controls how the device's state is set, based on the results of the command. The (Pg 1) section - defines the command-line, specifying the path to the executable, the command to execute, and any arguments to the command.

Sections Specific to Command-line Probes

The section defines the fields presented to the user in the Probe Configuration window.

Format the description using IMML, InterMapper's Markup language. Section specifies the help text that appears in the Set Probe window.

The

section of a command-line probe specifies the probe type, name, and a number of other properties fundamental to the operation of the probe.

In perl, C, C++, or your favorite language.) Your program's return value becomes the device's status on theĮach command-line probe follows the same general format as other probe files, sharing these common sections: InterMapper provides the ability to run a command-line probe, a script or program (written