This time I’d like to talk about the touchy issue when a service (you take charge of) does not function and you’re the last one to know about… Would’t you want to avoid this the next time it happens?
For instance,
If you take charge of ClearCase: don’t you want to know when a certain VOB stops functioning and users can’t check-out files?
If you take charge of Jenkins: don’t you want to know when a job is stuck, or runs more time than expected so all dependent downstream jobs can’t run?
If you take charge of ClearQuest: don’t you want to be the first one to know when users can’t query the ClearQuest database and get a list of defects or when users can’t submit a new defect?
If you answered YES to any of these questions, then you need a smart and lightweight monitoring & alerting system that can monitor the application layer .
Do you have such a system that fits the bill?
If not, ALM Vitality can do this for you, and it only takes about an hour to set it up and running, so you can start getting alerts about all of the aforementioned issues, plus many others, immediately!
Dashboard of ALM Vitality
Click to download ALM Vitality
Want to see the list of all monitored resources and learn more?
Click here
