Log entry when result pass into or out of compliance

A path monitor will log a message like this when the results of a monitoring session pass into or out of compliance with the requirements of a policy.

monitord[30173]: [Monitor 's4'][Policy 'cloud'] now compliant
monitord[30173]: [Monitor 's4'][Policy 'cloud'] no longer compliant

Log entry on marginal compliance

A path monitor will log a message like this if it determines that the compliance is marginal. That is, the results are in the tolerance range or the robustness count has been triggered.

monitord[30173]: [Monitor 's3'][Policy 'cloud'][Requirement 'round trip time'] Compliance is marginal (result above threshold by 11.856ms and robustness count is 1)

Log entry on failure to determine results

A path monitor will log a message like this if it cannot determine any results or cannot determine results with enough accuracy to determine the compliance state.

This may be because it cannot send any packets, or because it experiences a total loss of packets.

monitord[30173]: Monitor s2 failed

This message indicates that the results sample is considered to be out of compliance with all policies associated with path monitor 30173.

Log entry on failure to update due to a dataplane issue

A path monitor will log a message like this when it cannot update the policy compliance state in the dataplane because of a dataplane issue.

monitord[30690]: Failure running 'pathmonitor s3,cloud noncompliant' on dataplane:
                 Command '['/opt/vyatta/bin/vplsh', '-l', '-c', 'pathmonitor s3,cloud noncompliant']' returned non-zero exit status 1
monitord[30690]: [Monitor 's3'][Policy 'cloud'] Failed to implement policy compliance state 'False'

Log entry on failure to process monitoring results

A path monitor will log a message like this when it cannot process the monitoring results.

monitord[30173]: [Monitor 's4'][Policy 'cloud'] Receiving monitor results faster than they can be processed