From c4253716eb3972ed4173cd7dc70a69b7855c749b Mon Sep 17 00:00:00 2001 From: Steve Kemp Date: Thu, 6 Dec 2012 10:26:46 +0000 Subject: Identify the source of the alert. --- bytemark/bin/custodian-queue-monitor | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'bytemark') diff --git a/bytemark/bin/custodian-queue-monitor b/bytemark/bin/custodian-queue-monitor index 2320cc5..0b32370 100755 --- a/bytemark/bin/custodian-queue-monitor +++ b/bytemark/bin/custodian-queue-monitor @@ -15,7 +15,7 @@ max=5000 if ( custodian-queue --monitor=$max ) ; then - mauvesend alert.bytemark.co.uk -i custodian -c now -s "Our queue is too full" --detail="

The custodian queue doesn't seem to be emptying [alert threshold is $max].

Is there a bug, or do we need to add more workers? See https://wiki.bytemark.co.uk/Main/CustodianMonitoring

" + mauvesend alert.bytemark.co.uk -i custodian -c now -s "Our custodian queue is too full" --detail="

The custodian queue doesn't seem to be emptying [alert threshold is $max].

Is there a bug, or do we need to add more workers? See https://wiki.bytemark.co.uk/Main/CustodianMonitoring

" else - mauvesend alert.bytemark.co.uk -i custodian -r now -s "Our queue is too full" --detail="

The custodian queue doesn't seem to be emptying [alert threshold is $max].

Is there a bug, or do we need to add more workers? See https://wiki.bytemark.co.uk/Main/CustodianMonitoring

" + mauvesend alert.bytemark.co.uk -i custodian -r now -s "Our custodian queue is too full" --detail="

The custodian queue doesn't seem to be emptying [alert threshold is $max].

Is there a bug, or do we need to add more workers? See https://wiki.bytemark.co.uk/Main/CustodianMonitoring

" fi -- cgit v1.2.1