Difference between revisions of "Monitoring Notification Handling"

From Roaring Penguin
Jump to: navigation, search
(Created page with " what I sometimes recommend for situations like 38865 is this: (Note: Probably too difficult for most of our customers. :() 1) Make a secret subdomain like: notifications-x7p8nx…")
 
Line 1: Line 1:
what I sometimes recommend for situations like 38865 is this:  (Note: Probably too difficult for most of our customers. :()
+
What I sometimes recommend for situations like 38865 is this:  (Note: Probably too difficult for most of our customers.
 +
 
 
1) Make a secret subdomain like: notifications-x7p8nx.it-simplified.com and don't give it out.
 
1) Make a secret subdomain like: notifications-x7p8nx.it-simplified.com and don't give it out.
 +
 
2) Have mail for that domain go directly to your back-end server
 
2) Have mail for that domain go directly to your back-end server
 +
 
3) Configure all your monitoring tools to send to an address in that domain
 
3) Configure all your monitoring tools to send to an address in that domain
 +
 
4) Configure your back-end server to properly handle mail for that domain.
 
4) Configure your back-end server to properly handle mail for that domain.
 +
 
That takes one component (CanIt) that could delay mail out of the path.
 
That takes one component (CanIt) that could delay mail out of the path.
  

Revision as of 16:42, 23 January 2015

What I sometimes recommend for situations like 38865 is this: (Note: Probably too difficult for most of our customers.

1) Make a secret subdomain like: notifications-x7p8nx.it-simplified.com and don't give it out.

2) Have mail for that domain go directly to your back-end server

3) Configure all your monitoring tools to send to an address in that domain

4) Configure your back-end server to properly handle mail for that domain.

That takes one component (CanIt) that could delay mail out of the path.