There are two sides to performance management: rows and columns. We ask you to build a table of rows and columns in our mind – like a grid. We ask that you visualize this table only because actually drawing such a table is very complex.
The columns are resources that must be managed. It takes a lot of resources to deliver a screen of information to the user. These resources are typically managed by element managers and enterprise management systems. The enterprise often has a huge investment in these tools. Furthermore, the tools generally match the system architecture and organization chart. There are management systems for the network, servers, database, storage, etc.
This is referred to as silo management. There are good reasons to manage each silo independently – the technologies are very different. You wouldn’t want the network expert trying to figure out why one server with 10 users seems to be much slower that the other server with 1000 users.
Smart enterprises know that they can’t rely on each silo operating completely independently, so they implement “end-to-end” silo management. These systems provide an integrated view of all the silos on a single screen. The need for dashboards and simplification arises from the fact that an enterprise may easily have 6 to 12 or dozens of silos in operation, and each silo may encompass tens or hundreds of devices.
The rows are a completely different view of the system. This is the view as seen by the actual user’s traffic. A user session is made up of a flow of packets from the client machine through some of the elements of each silo and back again. This is often referred to as the horizontal cut or flow management view of the particular elements actually serving the user at a given time.
A single user task (traffic from when the user hits “Enter” to when the screen updates) takes up many rows. Each row is a series of packets or protocol events that bounce between a client and a server to complete the task. We refer to these individual round-trips as turns. In a business-to-business application built on a modern web-based architecture each user task typically requires 20 to 100 turns or rows in the table. That is 20 to 100 discrete measurements of events and performance at the transport layer.
The complete table of rows and columns provides the data necessary for comprehensive performance management (PM) but can easily have hundreds of columns and thousands of rows for just one hour of operation. The table in your mind may now have even more entries. The number of cells in this table is in the millions! Now you know why you may get headaches from time to time.
The table of rows and columns can only be managed with automated software. Software that provides a good view of each column and then integrates the columns into an end-to-end view is providing Infrastructure Performance Management (IPM). Conversely software that can identify application flows and report appropriate performance characteristics that show the user’s experience are providing Application Performance Management (APM).
You need a balance of both views. We recommend that you look at your management software capabilities and assess if you have an equal dose of both views.
