Skip to main content

Finding Your Organization’s Blind Spots

Steve Tack

How a Lifecycle Approach to APM Improves User Experience, Business Transaction Performance and Ultimately Revenues

Imagine it's Black Friday, when all of the sudden … boom! Your most critical Web application goes awry, bringing your e-commerce operation to a screeching halt on the very day flawless performance is needed most.

According to industry research cited in a Quocirca report titled “2012: The Year of Application Performance Management (APM)” a two second slowdown in response time is estimated to equal about four percent of revenue loss per visitor to an e-commerce site. So your organization probably doesn't have a lot of time to scramble to find out what is going wrong. You need to find answers – actionable information – and you need it fast.

The challenge to expeditious resolution is cutting through the vast amount of complexity that organizations are faced with today. First, there's the complexity involved in modern application delivery which is growing immensely. With applications increasingly pulling content from third-party services, and the advent of external infrastructures like the cloud, there are so many blind spots in the application delivery chain. Pinpointing the precise cause of application performance degradations can be tremendously difficult.

Second, there's the complexity that exists within organizations themselves, with so many stakeholders in application performance including developers, testers (QA), operations and line of business executives. Often, these groups are all speaking different business “languages” and concerned with different business goals.

For instance, developers speak in terms of debugging application code and don't want anything to impede their progress as they swiftly push out new products and enhancements. Operations, who wants to keep things as reliable and stable as possible, is quick to say “I told you so” whenever a problem arises. For their part, line of business speaks in numbers and they just want to know how conversions and revenues are being impacted – and when the bloodletting will stop!

This is a big mess which often results in a lot of wasted time, lack of meaningful communication and finger-pointing. One thing's for sure, “speed matters” – both in terms of actual application speed, as well as the speed at which performance problems are found, prioritized, addressed and fixed. Organizations desperately need a way to simplify all this complexity.

By now, you've more than likely heard the term DevOps, which entails bringing together developers and operations – both the pre-production and the production sides of the house. The goal is to aid in the release process, satisfying developers' requirements for speed while addressing operations' needs for stability. A key cornerstone of the DevOps movement is to commit to ongoing performance management and testing at all stages of an application lifecycle, from the earliest stages of development, to prevent problems from reaching production.

We at Compuware like to call this a lifecycle approach to performance management, since this term extends to include line of business executives. In order to successfully achieve a lifecycle approach, the proper type of APM system must be in place. First and foremost, this system must understand, from the user perspective, how applications and websites are performing. Achieving this level of insight requires monitoring of applications to go beyond the data center and start with the user perspective.

In addition, the proper type of APM system must:

- Deliver an integrated environment across stakeholders, to eliminate time spent correlating between different tools and to enable a common language of understanding. What applications are performing poorly? Why and whose problem is it? What's the impact on conversions?

- Provide automated, continuous visibility into what's going on – user behaviors, business transactions, conversion rates, etc.

- Offer actionable information for various stakeholders.

- Be application-centric as opposed to component-centric, which doesn't offer an overall view into how vital applications are performing. Additionally, be business aware, connecting IT to line of business by showing, for example, how IT is impacting the end- user experience and revenue.

In summary, it's important to remember that even the supposedly best application is never complete. Gartner estimates that only eight percent of an application's total cost of ownership (TCO) can be attributed to building, while the other 92 percent goes to ongoing enhancements, fixes and optimizationsi. A lifecycle approach to performance management, based on the right kind of APM solution, can help organizations navigate the vast complexity, ensure the strongest performing applications and make the best decisions that drive the user experience and revenues.

Steve Tack is VP of Product Management, Compuware APM.

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

Finding Your Organization’s Blind Spots

Steve Tack

How a Lifecycle Approach to APM Improves User Experience, Business Transaction Performance and Ultimately Revenues

Imagine it's Black Friday, when all of the sudden … boom! Your most critical Web application goes awry, bringing your e-commerce operation to a screeching halt on the very day flawless performance is needed most.

According to industry research cited in a Quocirca report titled “2012: The Year of Application Performance Management (APM)” a two second slowdown in response time is estimated to equal about four percent of revenue loss per visitor to an e-commerce site. So your organization probably doesn't have a lot of time to scramble to find out what is going wrong. You need to find answers – actionable information – and you need it fast.

The challenge to expeditious resolution is cutting through the vast amount of complexity that organizations are faced with today. First, there's the complexity involved in modern application delivery which is growing immensely. With applications increasingly pulling content from third-party services, and the advent of external infrastructures like the cloud, there are so many blind spots in the application delivery chain. Pinpointing the precise cause of application performance degradations can be tremendously difficult.

Second, there's the complexity that exists within organizations themselves, with so many stakeholders in application performance including developers, testers (QA), operations and line of business executives. Often, these groups are all speaking different business “languages” and concerned with different business goals.

For instance, developers speak in terms of debugging application code and don't want anything to impede their progress as they swiftly push out new products and enhancements. Operations, who wants to keep things as reliable and stable as possible, is quick to say “I told you so” whenever a problem arises. For their part, line of business speaks in numbers and they just want to know how conversions and revenues are being impacted – and when the bloodletting will stop!

This is a big mess which often results in a lot of wasted time, lack of meaningful communication and finger-pointing. One thing's for sure, “speed matters” – both in terms of actual application speed, as well as the speed at which performance problems are found, prioritized, addressed and fixed. Organizations desperately need a way to simplify all this complexity.

By now, you've more than likely heard the term DevOps, which entails bringing together developers and operations – both the pre-production and the production sides of the house. The goal is to aid in the release process, satisfying developers' requirements for speed while addressing operations' needs for stability. A key cornerstone of the DevOps movement is to commit to ongoing performance management and testing at all stages of an application lifecycle, from the earliest stages of development, to prevent problems from reaching production.

We at Compuware like to call this a lifecycle approach to performance management, since this term extends to include line of business executives. In order to successfully achieve a lifecycle approach, the proper type of APM system must be in place. First and foremost, this system must understand, from the user perspective, how applications and websites are performing. Achieving this level of insight requires monitoring of applications to go beyond the data center and start with the user perspective.

In addition, the proper type of APM system must:

- Deliver an integrated environment across stakeholders, to eliminate time spent correlating between different tools and to enable a common language of understanding. What applications are performing poorly? Why and whose problem is it? What's the impact on conversions?

- Provide automated, continuous visibility into what's going on – user behaviors, business transactions, conversion rates, etc.

- Offer actionable information for various stakeholders.

- Be application-centric as opposed to component-centric, which doesn't offer an overall view into how vital applications are performing. Additionally, be business aware, connecting IT to line of business by showing, for example, how IT is impacting the end- user experience and revenue.

In summary, it's important to remember that even the supposedly best application is never complete. Gartner estimates that only eight percent of an application's total cost of ownership (TCO) can be attributed to building, while the other 92 percent goes to ongoing enhancements, fixes and optimizationsi. A lifecycle approach to performance management, based on the right kind of APM solution, can help organizations navigate the vast complexity, ensure the strongest performing applications and make the best decisions that drive the user experience and revenues.

Steve Tack is VP of Product Management, Compuware APM.

The Latest

I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...