Advanced & experimental features

Experimental workarounds for unusual situations - among them calculating node status from sensors instead of network services, for nodes that cannot be reached normally.

Keep in mind that topics covered in this section are experimental workarounds

Monitoring status of a node without using network services

This option enables status calculation based on sensors - not network services. This may be especially useful if nodes aren't reachable by normal means (e.g., they are behind nat), and the only way of monitoring is to use sensors.

Enabling sensors-as-status

1. Add node where sensors should be used as a status
2. If there any network services present on the node - remove all of them via the node settings - monitoring tab.
3. Switch tab to 'properties' in the node settings and save node ID - it's located next to 'Identification,' e.g., #1234
4. Stop NetCrunch server service
5. Go to the NetCrunch data directory - by default C:\ProgramData\AdRem\NetCrunch\data\<id of the atlas> where the id of the atlas is represented by a digit (usually it's 2 if there was more than one atlas created in the NetCrunch - this number may differ.
6. Create a new text file inside the data folder - ipnodeOptions.json
7. Inside the file, add text like: [{"id":1234,"noServices":true}]
8. Save the file and start the server
9. Open node settings and add sensors that should be monitored; the important part is to disable event suppression (bell icon in the top right corner of the sensor settings window) on the sensors that were added to the node.