An important aspect of performance (and other) monitoring is where the observer stands when looking at the IT scenario. Each participant has a different view of what is bad performance - network, database, web, system, user personnel, management and external people - customers, regulatory bodies etc. These are what I call viewpoints, a popular concept in IT architecture design methods.
Start with APM and Viewpoints - Part 1
Operations people, but not the business user and others, will be desperately interested in:
■ % Utilizations
■ Wait times
■ Disk space used
■ Disk I/O Throughput
■ Disk I/O response time
■ Memory % used
■ Page rate
■ etc. etc.
End User Viewpoint
The previous factors are meaningless to the user of the application, who is more interested in:
■ Response times ( which depends on overall latency, percentiles, variations but they are not interested in that detail)
■ Variability of that response; large variations equal poor productivity via irritation and loss of concentration
■ Throughput of work where applicable
■ Other "speed" factors relating to their work
Business Manager Viewpoint
This viewpoint might reflect that of the end user is some respects, but will often be even more general:
■ What is the time between receipt of an order, shipment, invoicing and reconciliation?
■ Is the customer satisfied with this?
■ Can we speed up the processes without excessive cost?
■ Other business aspects
There are other people who will have different requirements and perspectives of performance: service desk, external customers, especially website users, and possibly regulatory bodies. They are important and in performance life, one size does not fit all.
When considering performance management, which is more than simply monitoring, the differing requirements (viewpoints) of various stakeholders needs to be taken into account. It is often difficult to retrofit analysis of performance data to cater for people not considered at the design stage. You may be asked by the CEO, out of the blue: "Why do we take 2 days to issue an invoice after shipment while competitor X takes one?"
Role of the SLA
Whose level of service (quality of service, QoS) are we talking about? Basically, all the types of person outlined above. This (rather these) QoS are usually formalized in a Service Level Agreement or SLA. This will dictate what needs to be measured and analyzed:
"If you can't measure it or derive it, you can't report it."
"A service-level agreement (SLA) is a contract between a service provider and its internal or external customers that documents what services the provider will furnish and defines the performance standards the provider is obligated to meet." [WhatIs.com].
The trick here is to marry these viewpoints which means translating the operational data into service level agreement (SLA) terms and hence into stakeholder perspective, another word for viewpoint All this is complicated when one moves from the relatively simple classical IT environment to the mixed web and application environments, rendered even more difficult to fathom by virtualization and clouds.
There is no reason why external customers shouldn't be part of any SLA drawn up if the APM setup is designed to cover all important stakeholders.
In addition, it should be transparent to the stakeholders outside operations whether the system runs native, virtualized, in a cloud or in a series of school exercise books. The APM design with these differing viewpoints in mind is the key aspect of this.
Dr. Terry Critchley is the Author of "Making It in IT", "High Performance IT Services" and “High Availability IT Services”.
This blog was created from extracts from Terry Critchley's book: High Performance IT Services [ August 25 2016]
According to most industry perceptions, application performance management (APM) and application portfolio management (APM) might seem to be worlds apart — or at best connected by a very thin thread. In this blog, I'd like to highlight three areas that are bridging the APM-to-APM divide: digital experience management, application discovery and dependency mapping (ADDM), and agile/DevOps lifecycle planning ...
In today's digital world, it is possible to gauge the cost implications of an IT outage on employee productivity, revenue generation but it is usually much more tricky to measure the negative impacts on the very IT people's lives ...
APMdigest asked experts across the industry for their opinions on the next steps for ITOA. Part 5 offers some interesting final thoughts ...
APMdigest asked experts across the industry for their opinions on the next steps for ITOA. Part 4 covers automation and the dynamic IT environment ...
APMdigest asked experts across the industry for their opinions on the next steps for ITOA. Part 3 covers monitoring and user experience ...
APMdigest asked experts across the industry for their opinions on the next steps for ITOA. Part 2 covers visibility and data ...
Managing application performance today requires analytics. IT Operations Analytics (ITOA) is often used to augment or built into Application Performance Management solutions to process the massive amounts of metrics coming out of today's IT environment. But today ITOA stands at a crossroads as revolutionary technologies and capabilities are emerging to push it into new realms. So where is ITOA going next? With this question in mind, APMdigest asked experts across the industry — including analysts, consultants and vendors — for their opinions on the next steps for ITOA ...
Digital transformation initiatives are more successful when they have buy-in from across the business, according to a new report titled Digital Transformation Trailblazing: A Data-Driven Approach ...
The growing market for analytics in IT is one of the more exciting areas to watch in the technology industry. Exciting because of the variety and types of vendor innovation in this area. And exciting as well because our research indicates the adoption of advanced IT analytics supports data sharing and joint decision making in a way that's catalytic for both IT and digital transformation ...
Colin Fletcher, Research Director at Gartner, talks about Algorithmic IT Operations (AIOps) and the challenges and recommendations for AIOps adoption ...