Introduction

In some circumstances you might not wish to monitor a node via SNMP. You might not be able to because of credentials, the node may not be running SNMP or any other reason. But you still want to be able to check various websites are running upon it. This is where a ServiceOnly node comes in.

Options

NMIS is quite flexible, but regardless of how you want to monitor a node, you will need to tell NMIS what to check. To do this we have two options - one node with multiple service checks or multiple nodes with a single service check each.

Create a Node

Add the node as normal, but set:

...

That combination of attributes will make NMIS automatically declare the node to be a ServiceOnly node. You can see this when looking at the Model node property.

One Node Multiple

...

Service Checks

Create the node as per above but supply a node name that makes sense. Maybe something like "Node For WebTest".

...

Add a new service check as above for each URL / webpage you want to monitor.

Done!

Multiple Nodes Single

...

Service Check

For each URL you want to monitor, create a node as above.

...

In this case, we can utilize a single instance of our service check as below. This will insert the Node FQDN (or IP) into the service check.

Done!

Wrapping Up

One way or the other, we need to tell NMIS "this is the list of URLs to be checked". Weather we use a single node with multiple service checks or multiple nodes with single service checks is completely your decision. There is no difference in the amount of information you need to provide NMIS, you simply provide it in different ways.

...