Auto going down after few second coming up
error message is
0.02 error #/s (Errors) is above the error limit of < 0.01 #/s
please advice to me
syslog error
Votes:
0
1 Reply
Votes:
0
Hello.
By default, the Syslog Receiver Sensor has the following Warning/Error definitions:
- Warning Filter: severity[4]
- Error Filter: severity[0-3]
Please note how the Syslog Receiver and SNMP Trap Receiver Sensors behave:
Incoming messages are counted per scanning interval, so it might take a few moments to see the received syslogs/traps, depending on the remaining time until the next sensor scan. Of course, you can use Check Now via the sensor's context buttons to perform an immediate scan and see corresponding data. The sensor states are also defined per scan.
So, for example, a message which is classified as error will count for the error channel only for one scanning interval; if there is no new error message in the following scanning interval, no message is shown in the error channel anymore and the error status will disappear after the next sensor scan. The syslog or trap itself will still be accessible on the Messages tab.
For further clarification, please check:
PRTG Manual: Syslog Receiver Sensor
Paessler website: How to monitor syslog and SNMP trap messages in 6 steps
Best Regards,
Created on Jul 10, 2015 6:31:18 AM by
Last change on Feb 28, 2023 3:01:53 PM by
Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.
Add comment