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]
While remote work policies have been gaining steam for the better part of the past decade across the enterprise space — driven in large part by more agile and scalable, cloud-delivered business solutions — recent events have pushed adoption into overdrive ...
Time-critical, unplanned work caused by IT disruptions continues to plague enterprises around the world, leading to lost revenue, significant employee morale problems and missed opportunities to innovate, according to the State of Unplanned Work Report 2020, conducted by Dimensional Research for PagerDuty ...
In today's iterative world, development teams care a lot more about how apps are running. There's a demand for fixing actionable items. Developers want to know exactly what's broken, what to fix right now, and what can wait. They want to know, "Do we build or fix?" This trade-off between building new features versus fixing bugs is one of the key factors behind the adoption of Application Stability management tools ...
With the rise of mobile apps and iterative development releases, Application Stability has answered the widespread need to monitor applications in a new way, shifting the focus from servers and networks to the customer experience. The emergence of Application Stability has caused some consternation for diehard APM fans. However, these two solutions embody very distinct monitoring focuses, which leads me to believe there's room for both tools, as well as different teams for both ...
The 2019 State of E-Commerce Infrastructure Report, from Webscale, analyzes findings from a comprehensive survey of more than 450 ecommerce professionals regarding how their online stores performed during the 2019 holiday season. Some key insights from the report include ...
Robinhood is a unicorn startup that has been disrupting the way by which many millennials have been investing and managing their money for the past few years. For Robinhood, the burden of proof was to show that they can provide an infrastructure that is as scalable, reliable and secure as that of major banks who have been developing their trading infrastructure for the last quarter-century. That promise fell flat last week, when the market volatility brought about a set of edge cases that brought Robinhood's trading app to its knees ...
Application backend monitoring is the key to acquiring visibility across the enterprise's application stack, from the application layer and underlying infrastructure to third-party API services, web servers and databases, be they on-premises, in a public or private cloud, or in a hybrid model. By tracking and reporting performance in real time, IT teams can ensure applications perform at peak efficiency — and guarantee a seamless customer experience. How can IT operations teams improve application backend monitoring? By embracing artificial intelligence for operations — AIOps ...
In 2020, DevOps teams will face heightened expectations for higher speed and frequency of code delivery, which means their IT environments will become even more modular, ephemeral and dynamic — and significantly more complicated to monitor. As a result, AIOps will further cement its position as the most effective technology that DevOps teams can use to see and control what's going on with their applications and their underlying infrastructure, so that they can prevent outages. Here I outline five key trends to watch related to how AIOps will impact DevOps in 2020 and beyond ...
With the spread of the coronavirus (COVID-19), CIOs should focus on three short-term actions to increase their organizations' resilience against disruptions and prepare for rebound and growth, according to Gartner ...
Whether you consider the first generation of APM or the updates that followed for SOA and microservices, the most basic premise of the tools remains the same — PROVIDE VISIBILITY ...