Saturday, April 5, 2014

In defense of regular alerting - Part 2

Following up on the first installment of this idea, today I bring you yet another reason to put in regular alerting on your system.

How many sessions do you have coming into your system?  Is your EBS system a spider in the middle of an ever increasingly complex web?  If you are not sure about what is coming into your system, can you swear that the system is working as intended?

In my newest alert to monitor the sessions coming in to our EBS from other servers in our ecosystem, a pleasant side effect is that we could see what server/user combinations had 0 connections.  What does that mean for us?  Well, in this instance we could actually tell when the other server had been bounced and the services did not come back up automatically.  This means we can get to another level of proactivity by seeing an issue before the business reports it AND help out our IT partners by alerting them to this condition if they were not already aware of it.

No comments:

Post a Comment