Skip to main content

Make a Better Business Case for End-to-End Monitoring

Ted Wilson

Monitoring your middleware platforms with a consolidated monitoring application has been shown over and over to reduce the frequency and duration of severity 1 and 2 incidents and prevent losses of revenue attributed to downtime. However, making a strong business care for end-end monitoring and middleware monitoring can be challenging and can present unique learning opportunities. Here are some recommendations to help you make a better business case.

1. Use tangible benefits and savings only

Annual outage volume, agreed-upon Mean-Time-to-Resolution (MTTR) times, and Service Level Agreement (SLA) penalties are the most common. Soft benefits such as better use of IT resources, reduces damage to the brand, and fewer people on conference calls will certainly provide a benefit, but a hard savings is difficult to quantify and should probably not be included in the financial justification.

One large bank had as many as 115 people on their war room conference calls. And calls averaged several hours with one call last year taking 27 hours! While there is certainly a productivity gain to be made, your finance team is unlikely to agree on a hard savings amount by eliminating some of these calls.

2. Start small and pick the right application for your proof of concept

The “right” application should be one that will bridge the gap between the technology and the business. It is always great if you can quantify results based on your application or service running in your environment.

3. Get your main detractors socialized in this process as early as you can

This is not a popularity contest and you are probably going to be shining a bright light on some problem areas. But your detractors can become your biggest supporters once they are able to work with a common version of the truth that is based on actual performance data. They don’t have to miss out on many war room conferences to see the value in effective end-to-end monitoring.

4. Ensure the financial portion of the business case is conservative

Ensure that the financial portion of the business case is conservative and none of the assumptions can be argued by your finance team. Use internally available data obtained from the business owners, support teams, and your trouble ticketing system administrator. And remember that it is better to underestimate your savings and overestimate your costs. You want to show a fast payback based on conservative numbers that cannot be argued.

Ted Wilson is Chief Operating Officer at SL Corporation.

Hot Topics

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 ...

Make a Better Business Case for End-to-End Monitoring

Ted Wilson

Monitoring your middleware platforms with a consolidated monitoring application has been shown over and over to reduce the frequency and duration of severity 1 and 2 incidents and prevent losses of revenue attributed to downtime. However, making a strong business care for end-end monitoring and middleware monitoring can be challenging and can present unique learning opportunities. Here are some recommendations to help you make a better business case.

1. Use tangible benefits and savings only

Annual outage volume, agreed-upon Mean-Time-to-Resolution (MTTR) times, and Service Level Agreement (SLA) penalties are the most common. Soft benefits such as better use of IT resources, reduces damage to the brand, and fewer people on conference calls will certainly provide a benefit, but a hard savings is difficult to quantify and should probably not be included in the financial justification.

One large bank had as many as 115 people on their war room conference calls. And calls averaged several hours with one call last year taking 27 hours! While there is certainly a productivity gain to be made, your finance team is unlikely to agree on a hard savings amount by eliminating some of these calls.

2. Start small and pick the right application for your proof of concept

The “right” application should be one that will bridge the gap between the technology and the business. It is always great if you can quantify results based on your application or service running in your environment.

3. Get your main detractors socialized in this process as early as you can

This is not a popularity contest and you are probably going to be shining a bright light on some problem areas. But your detractors can become your biggest supporters once they are able to work with a common version of the truth that is based on actual performance data. They don’t have to miss out on many war room conferences to see the value in effective end-to-end monitoring.

4. Ensure the financial portion of the business case is conservative

Ensure that the financial portion of the business case is conservative and none of the assumptions can be argued by your finance team. Use internally available data obtained from the business owners, support teams, and your trouble ticketing system administrator. And remember that it is better to underestimate your savings and overestimate your costs. You want to show a fast payback based on conservative numbers that cannot be argued.

Ted Wilson is Chief Operating Officer at SL Corporation.

Hot Topics

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 ...