This article provides information about how to report errors and alarms from your probe.
Reporting an Error When a Probe Cannot Connect to a Resource
During the getUpdatedInventory() collection cycle, the probe typically connects to the target system specified in the profile. If there is a problem making that connection and gathering data, the probe should report this by throwing a NimException. The framework will catch this and create an alarm.
Explicitly Send an Alarm
Under normal operating conditions a probe developer should not be concerned with sending alarms. The probe framework will generate the appropriate alarms when metrics breach configured thresholds. In the case of an abnormal situation that a probe cannot recover from, a NimException should be thrown by the probe. The framework will catch the NimException and send an associated alarm.