There is a difference between monitoring technology and understanding the impact of technology on your business.

One of the most stressful times for any online business is dealing with performance and availability issues that were reported by your customers. If the customer saw an issue and reported it, things are bad, the clock is ticking, and you are looking to get this back on track with the least amount of damage. You’ve already lost some satisfaction points, and the goal now is to lose the least you possibly can. This is never a good place to be. No one wants to be in this position!

We are all primed to win, not lose least.

The issue comes down to the fact that today’s complex business applications have an incredible number of moving parts, and the interaction between all these parts can lead to unexpected outcomes. While in “days of old”, performance monitoring meant looking for systems that were either running too hot (exceeding their processing limits) or had stopped running, today it’s normal to see the interaction between a dozen systems (all running within their expected limits) cause an unexpected bottleneck or loop-back that leads to a poor user experience. And poor user experiences lead to lost customers, lost deals and a loss of satisfaction, all of which are not good.

So how can you improve the situation?

Quite simply by understanding the user experience at a qualitative and quantitative level. You can do this by using a function that already exists with your application stack, but that is not normally exploited. All of the systems within your application stack must be connected together using systems designed to manage the flow of interactions, this is the middleware system. These systems send messages that are queued between every application. By reading and understanding the contents of these middleware messages you directly understand the “business” that is taking place. You can weave these messages together to describe exactly how a user’s business request is serviced through the entire application stack. This is an abstraction of business created from the technology. Using this you can see every user’s business being performed and you can notice the subtle indicators of any change that may lead to any issue.

By itself creating a business abstraction of the technology is just part of the answer, when you combine this with the detailed monitored information that underlies it, you have something new and incredibly powerful. You now have a multi-dimensional perspective of your business that combines an understanding of the business and an understanding of how the technology is performing. You can now be pro-active in identifying issues and you can be predictive, allowing you to understand how likely an issue in the future is to happen. This means you can start to solve issues that have not even happened yet, and will not happen, because you will take remedial action to reduce the chance of even these risks from happening.

Now you’re delivering monitoring for the modern age, pro-active and predictive performance and availability monitoring that truly reduces the time to solve problems to the point where they are solved in negative time.

This is what Nastel is delivering right now