Question
Anzelem Sanyatwe · Nov 14, 2016

Cache Monitor (^MONMGR)/System Monitor and Email Alerts - No 'OK' messages are send!

Can Cache Monitor (^MONMGR) and System Monitor be configured to also send 'OK' messages? With the first bad email, you still wonder if things are still broken, when in-fact normalcy has been restored, some even within some seconds.

typical examples : -

------ - - - -- - - - -- - -- --- - -- -- -- - - - -- -- -- - --- - - - -- - - -- - - -- --- - - -- -- -- - - --- - - - - --- -- --- - - -- -- --- - - --- - --- -- - - -- -

Sent: Monday, 14 November 2016 11:51 AM

To: Email

Subject: [CACHE SEVERE ERROR :ENSEMBLE] CP: Pausing users because Journal Daemon has not shown

11/14/16-11:50:43:430 (3455) 2 CP: Pausing users because Journal Daemon has not shown     signs of activity for 338 seconds. Users will resume if Journal Daemon is active again

- - - -- -  - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- - - - - - - - - - - -

-----Original Message-----
Sent: 14 November 2016 12:39 AM
To: Email
Subject: [CACHE SEVERE ERROR :ENSEMBLE] [SYSTEM MONITOR] WriteDaemon Alert: Write Daemon still on pass 1112

11/14/16-00:39:09:735 (74654) 2 [SYSTEM MONITOR] WriteDaemon Alert: Write Daemon still on pass 1112

-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

The above did not send the 'OK' message, if you go and check the console.log, you will notice that the error would have been cleared, some within seconds.

11/14/16-11:50:42:451 (3455) 0 Journal Daemon appears inactive with I/O pending:
gjrnoff=243209152,iocomplete=243164228,filecnt=20637,fail=0
11/14/16-11:50:43:430 (3455) 2 CP: Pausing users because Journal Daemon has not shown
    signs of activity for 338 seconds. Users will resume if Journal Daemon is active again
11/14/16-11:50:44:536 (3455) 0 Journal Daemon has shown signs of activity, allowing users to proceed
 

11/14/16-00:39:09:735 (74654) 2 [SYSTEM MONITOR] WriteDaemon Alert: Write Daemon still on pass 1112
11/14/16-00:40:40:865 (74654) 0 [SYSTEM MONITOR] WriteDaemon Alert: Write Daemon completed a pass.
 

 

1
1 1,371
Discussion (1)2
Log in or sign up to continue

The ^MONMGR utility just send mails based on the severity of the messages in the cconsole.log. In order to find the severity in the cconsole.log you can look at the number after the date and process id. 

11/14/16-00:39:09:735 (74654) 2 [SYSTEM MONITOR] WriteDaemon Alert: Write Daemon still on pass 1112
11/14/16-00:40:40:865 (74654) 0 [SYSTEM MONITOR] WriteDaemon Alert: Write Daemon completed a pass.

In that case we can see severity 2 for the first message and 0 for the second one (The OK one). As the default severity level in ^MONMGR is 2, it will only send mails when it's 2 or higher.  Note that you can change this level from the MONMGR menu, but lowering to 0 or 1 will give you lots of messages which probably you don't want. 

Anyway, after getting any 2 level message, the recommendation is to review the logs and find what caused the problem. If is a puntual error and was solved by itself (like the one you described) you should not worry. If you keep getting such messages my recommendation is to investigate and contact with Intersystems support if you need help.