Installation

In order to install the dbWatch Nimsoft extension you need two files

  • nimbus.jar
  • nimbuspump.jar

They can be downloaded from the following locations:
https://download.dbwatch.com/download/extensions/nimbus/nimbus.jar
https://download.dbwatch.com/download/extensions/nimbus/nimbuspump.jar

Place nimbus.jar in the [dbWatch Server]/lib/ catalog.
Place nimbuspump.jar in the [dbWatch Server]/server/extensions/ catalog.

You will need to restart the dbWatch Server in order for these files to be loaded correctly. Verify that the extension is loaded by navigating to the “Server”->“Server Extensions” menu in the dbWatch Monitor. This should open the Extensions view, where you should see an entry called Nimbus Extension.

You are now ready to configure the extension.

Configuration

In the Extensions view, select the Nimbus extension entry and click «configure». This should open the configuration panel as shown below.

The possible configurations are:

react-to
Defines what types of signals should be sent. Possible values are:
ENGINE-WARNING, ENGINE-ALARM, ENGINE-LOSTCONNECTION,
ENGINE-OK, EXCEPTION

alarm-level
Defines the nimbus level an alarm in dbWatch should correspond to.
1 = INFORMATION, 2 = WARNING, 3 = MINOR, 4 = MAJOR, 5 = CRITICAL

warning-level
Defines the nimbus level a warning in dbWatch should correspond to.
1= INFORMATION, 2 = WARNING, 3 = MINOR, 4 = MAJOR, 5 = CRITICAL

connection-lost-level
Defines the nimbus level a lost connection signal in dbWatch should
correspond to. 1 = INFORMATION, 2 = WARNING, 3 = MINOR, 4 =
MAJOR, 5 = CRITICAL

executable
Full path to the nimalarm executable.

check-message-format
Defines the format a warning/alarm message from dbWatch should
have. STATUS will be replaced by a string describing the level of
the signal (ALARM or WARNING). GIVENNAME will be
replaced by the name of the database instance concerning this signal.
CHECK-DETAILS will be replaced by a string describing the
name and details of the signal check this concerns.

exception-messageformat
Defines the format an exception message from dbWatch should have.
EXCEPTION-MESSAGE will be replaced by a text describing the
exception.

lost-connectionmessage-format
Defines the format a lost connection signal from dbWatch should have.
GIVENNAME will be replaced by the name of the database
instance.

debug
Checkbox indicating the debug information should be written to the
dbWatch log.

Once you are satisfied with your settings, click «OK».
In the Extensions view, select the Nimbus extension entry again, and click «Enable»

Configuration on the Nimsoft side

The dbWatch Nimsoft extension works by invoking the nimalarm executable in the following ways:

For check warning

nimalarm -l warning-level -s dbWatch -c givenname -S host check-message-format

Example:

C:/Program Files/NimBUS/bin/nimalarm.exe -l 2 -s dbWatch -c TestDB -S 192.168.0.234 "dbWatch
Server WARNING detected on TestDB (Disk space check: Warning for drive F: 1.5GB)"

For check alarm

nimalarm -l alarm-level -s dbWatch -c givenname -S host check-message-format

Example:

C:/Program Files/NimBUS/bin/nimalarm.exe -l 5 -s dbWatch -c TestDB -S 192.168.0.234 "dbWatch
Server ALARM detected on TestDB (Disk space check: Alarm for drive F: 0.5GB)"

For lost connection

nimalarm -l connection-lost-level -s dbWatch -c givenname -S host lost-connection-message-format

Example:

C:/Program Files/NimBUS/bin/nimalarm.exe -l 4 -s dbWatch -c TestDB -S 192.168.0.234 "dbWatch
Server lost connection to TestDB"

For exception

nimalarm -l 1 -s dbWatch exception-message-format

Example:

C:/Program Files/NimBUS/bin/nimalarm.exe -l 1 -s dbWatch "Out of memory exception detected
on dbWatch"

For details on how to handle these signals in Nimsoft, refer to your Nimsoft documentation

← HP OpenView / Nagios →

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment