Summary: | Monitor mail queue on mail01.ipfire.org | ||
---|---|---|---|
Product: | Infrastructure | Reporter: | Peter Müller <peter.mueller> |
Component: | Monitoring | Assignee: | Michael Tremer <michael.tremer> |
Status: | CLOSED FIXED | QA Contact: | Peter Müller <peter.mueller> |
Severity: | - Unknown - | ||
Priority: | - Unknown - | CC: | morlix |
Version: | unspecified | ||
Hardware: | unspecified | ||
OS: | Unspecified | ||
See Also: | https://bugzilla.ipfire.org/show_bug.cgi?id=11765 | ||
Bug Depends on: | |||
Bug Blocks: | 11768 |
Description
Peter Müller
2018-06-11 18:21:49 UTC
What would the thresholds be and potential actions? Treshold: 100 (warning), 250 (critical) Actions: Depends on the situation. If we just have a lot of traffic to a bogus destination (DTAG, for example), we might just have to wait. Most important aspect here is to get notified. Apologies for being a bit too busy to google right now, but I will have to write something that allows us to extract that data via SNMP. I don't want to distribute SSH keys for running monitoring checks if I can avoid it. (In reply to Michael Tremer from comment #3) > Apologies for being a bit too busy to google right now, but I will have to > write > something that allows us to extract that data via SNMP. I don't want to > distribute SSH keys for running monitoring checks if I can avoid it. Let me google that for you... :-) Maybe this is helpful: https://conshell.net/wiki/Using_Nagios_with_SNMP (Basically there is a Nagios plugin for monitoring the mail queue, "/usr/local/nagios/libexec/check_mailq", which can be added to SNMP). Could you set this up? Done. |