|
From: | Joseph Larsen |
Subject: | Re: monit-general Digest, Vol 163, Issue 20 |
Date: | Thu, 18 Aug 2016 11:16:55 -0600 |
Send monit-general mailing list submissions to
address@hidden
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.nongnu.org/mailman/listinfo/monit-general
or, via email, send a message with subject or body 'help' to
address@hiddenorg
You can reach the person managing the list at
address@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of monit-general digest..."
Today's Topics:
1. Re: node.js watching for errors (Martin Pala)
------------------------------------------------------------ ----------
Message: 1
Date: Thu, 18 Aug 2016 14:21:52 +0200
From: Martin Pala <address@hidden>
To: This is the general mailing list for monit
<address@hidden>
Subject: Re: node.js watching for errors
Message-ID: <2E088A63-21ED-46F7-821D-address@hidden >
Content-Type: text/plain; charset=utf-8
It depends which traces the exception left ... if the exception is logged to some logfile, you can use the "check file" statement with content test.
Best regards,
Martin
> On 17 Aug 2016, at 18:47, Joseph Larsen <address@hidden> wrote:
>
> I?m using monit to watch a few node.js servers that i?m running. So far, so good. My question, if they are stopped it?s almost always because an uncaught exception happened. Is there a way to use monit to email me the exception(s) that caused the server to die?
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
------------------------------
Subject: Digest Footer
_______________________________________________
monit-general mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/monit-general
------------------------------
End of monit-general Digest, Vol 163, Issue 20
**********************************************
[Prev in Thread] | Current Thread | [Next in Thread] |