40 Posts
0
521
A possible monitoring display bug for Probe action check result in Networker?
According to the Networker documentation, when there is a probe action in a workflow, only is the return code of 0 from the execution of the probe script considered as probe check success, and the following other (backup or clone) actions will be executed. In Monitoring window of Networker Administration, the probe action would be marked with a green check if the probe script returns 0. When the execution of the probe script returns other codes like 3, 7 or -3, the probe action would be marked with a red cross in the Monitoring window, and the following actions would not be executed. The only exception is when the return code is 1. In that case, the probe action is marked with a green check, looks like a successful probe check; but the following actions in the workflow would not be executed because the return code of 1 means a probe check failure. Why the return code of 1 from the probe script is marked with a green check in the Monitoring windows? Is this done on purpose or a possible display bug? I found this issue in both Networker 18.2 and 19.1.
crazyrov
4 Operator
4 Operator
•
1.3K Posts
0
August 29th, 2020 00:00
@ChiXC, The probe actually allows either 1 or 0. The rest of the return type means the probe did not receive what it expected to receive thus the failed notification. The 1 and 0 are just indications that backup is not required and thus logic should be controlled by the script on the client that the probe is going to initiate. A failure means that things aren't going as you intend it to but a return of 1 and 0 is intended to control if a backup is required or not and thus is not actually a failure and thus marked as successful. This makes more sense when you have a automated ticketing system which created incident tickets automatically on failed jobs.
ChiXC
40 Posts
0
August 28th, 2020 12:00
What do you mean you need a solution to fix the issue? This is just a possible display mistake. When the return code of your probe action is 1, the NMC Monitoring shows a green check as a successful probe check. But the initial logic will treat the probe action failed. No of the following actions will run. So this is just a display mistake, there is no logic issue!
ChiXC
40 Posts
0
August 29th, 2020 08:00
@crazyrovThanks for the explanation. That is a quite interesting design choice: a green check in Monitoring shows a "successful" Probe check action. But whether the following backup/clone actions should take place depends on the return code of a "successful" probe! A successful probe marked by the green check doesn't mean the pre-condition for the backup is met! I am not sure this is very intuitive: a green check mark for a backup action in Monitoring means the backup completed successfully or just means the backup action took place but not sure if backup succeeded or not. Anyway if this is the "design choice", we just need to accept it and adjust our own perception.