Skip to main content

As CIOs Address App Sprawl, Observability Can't Be an Afterthought

Bill Lobig
IBM Software

App sprawl has been a concern for technologists for some time, but it has never presented such a challenge as now. As organizations move to implement generative AI into their applications, it's only going to become more complex. In fact, a recent Canva report found that 72% of CIOs see application sprawl as a challenge — and with 71% of CIOs expecting to adopt 30-60 new apps this year, this complexity is poised to keep growing.

Potential solutions include consolidating applications, optimizing workflows, and automating IT processes to reduce strain on technologists so they can tackle the issue of app sprawl head-on. While these are all valid and necessary approaches, observability is a necessary component for understanding the vast amounts of complex data within AI-infused applications, and it must be the centerpiece of an app- and data-centric strategy to truly manage app sprawl.

Cracking the Code for AI App Sprawl Challenges

In a year of elevated global IT spend, ensuring investments aren't wasted is a necessity for overwhelmed technology leaders, who not only must make decisions around which technologies to implement, but also make sense of application performance amid growing tides of vast and complex data.

When AI enters the mix, it's even more important to have complete visibility, which many organizations still lack. Observability tools and practices can help technologists address AI app sprawl by providing visibility into the performance, behavior, and dependencies of AI applications. Unfortunately, many teams are still attempting to work with incomplete visibility, meaning they simply don't know what they don't know.

Simply put, traditional application performance monitoring (APM) tools can provide visibility to a certain degree, but they weren't built to necessarily account for the influx of generative AI applications that modern enterprises are dealing with.

End-users for generative AI-infused applications demand continuous availability and frictionless experience. However, with a lack of real-time visibility, they will feel when an outage or delay compromises their experience, particularly as applications span numerous platforms. Not to mention, the implementation and understanding of complex generative AI models' behaviors are still something many organizations are working to figure out. These potential blind spots could create significant performance, compliance, and security issues.

Observe the Full Stack So You Can Add to It

Organizations can better understand the internal state of their AI applications by analyzing their external outputs with observability. When this is connected to business outcomes and effectively addressed, technology teams can lay the groundwork for a well-functioning application monitoring and management process. So, when generative AI is introduced to the environment, the foundation is already in place to effectively see and optimize application processes.

As generative AI applications join the enterprise equation, observability tools are a must-have for facilitating the delivery of higher-quality software at a faster pace — these are best enabled through:

Finding and fixing the "unknown unknowns": You can't fix what you can't see. Unfortunately, many monitoring practices and tools can only address flaws that are previously known. Observability uncovers conditions that would be impossible to find manually or with traditional platforms. It then monitors the correlation to different performance flaws and gives context for discovering root causes, resulting in quick and easy remediation.

Detecting and remediating issues early on: With observability, monitoring is integrated into the initial stages of software development. It's then easy to pinpoint and rectify new code issues before they affect the service level agreements (SLAs) and customer experience.

Self-healing application infrastructure and automated resolution: Observability can be coupled with automation capabilities to anticipate issues from system outputs and resolve them autonomously without requiring manual intervention.

Scaling and load balancing: We need to be able to observe and control the current load on systems but also help forecast future demands. The data can be used to optimize applications in real-time without having the end-users feel any impact.

Cost management: From optimizing workloads to computational resources, SREs can and should find ways to save on VM, GPU, cloud and inferencing costs through observability.

Observability is crucial for organizations to address AI app sprawl and overcome myriad challenges that come along with it, especially as generative AI becomes a mainstay across enterprises. By following observability best practices and deploying the right automated tools, organizations can proactively identify and resolve issues and ensure all AI applications are always available and friction-free.

Bill Lobig is VP, Automation Product Management, IBM Software

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

As CIOs Address App Sprawl, Observability Can't Be an Afterthought

Bill Lobig
IBM Software

App sprawl has been a concern for technologists for some time, but it has never presented such a challenge as now. As organizations move to implement generative AI into their applications, it's only going to become more complex. In fact, a recent Canva report found that 72% of CIOs see application sprawl as a challenge — and with 71% of CIOs expecting to adopt 30-60 new apps this year, this complexity is poised to keep growing.

Potential solutions include consolidating applications, optimizing workflows, and automating IT processes to reduce strain on technologists so they can tackle the issue of app sprawl head-on. While these are all valid and necessary approaches, observability is a necessary component for understanding the vast amounts of complex data within AI-infused applications, and it must be the centerpiece of an app- and data-centric strategy to truly manage app sprawl.

Cracking the Code for AI App Sprawl Challenges

In a year of elevated global IT spend, ensuring investments aren't wasted is a necessity for overwhelmed technology leaders, who not only must make decisions around which technologies to implement, but also make sense of application performance amid growing tides of vast and complex data.

When AI enters the mix, it's even more important to have complete visibility, which many organizations still lack. Observability tools and practices can help technologists address AI app sprawl by providing visibility into the performance, behavior, and dependencies of AI applications. Unfortunately, many teams are still attempting to work with incomplete visibility, meaning they simply don't know what they don't know.

Simply put, traditional application performance monitoring (APM) tools can provide visibility to a certain degree, but they weren't built to necessarily account for the influx of generative AI applications that modern enterprises are dealing with.

End-users for generative AI-infused applications demand continuous availability and frictionless experience. However, with a lack of real-time visibility, they will feel when an outage or delay compromises their experience, particularly as applications span numerous platforms. Not to mention, the implementation and understanding of complex generative AI models' behaviors are still something many organizations are working to figure out. These potential blind spots could create significant performance, compliance, and security issues.

Observe the Full Stack So You Can Add to It

Organizations can better understand the internal state of their AI applications by analyzing their external outputs with observability. When this is connected to business outcomes and effectively addressed, technology teams can lay the groundwork for a well-functioning application monitoring and management process. So, when generative AI is introduced to the environment, the foundation is already in place to effectively see and optimize application processes.

As generative AI applications join the enterprise equation, observability tools are a must-have for facilitating the delivery of higher-quality software at a faster pace — these are best enabled through:

Finding and fixing the "unknown unknowns": You can't fix what you can't see. Unfortunately, many monitoring practices and tools can only address flaws that are previously known. Observability uncovers conditions that would be impossible to find manually or with traditional platforms. It then monitors the correlation to different performance flaws and gives context for discovering root causes, resulting in quick and easy remediation.

Detecting and remediating issues early on: With observability, monitoring is integrated into the initial stages of software development. It's then easy to pinpoint and rectify new code issues before they affect the service level agreements (SLAs) and customer experience.

Self-healing application infrastructure and automated resolution: Observability can be coupled with automation capabilities to anticipate issues from system outputs and resolve them autonomously without requiring manual intervention.

Scaling and load balancing: We need to be able to observe and control the current load on systems but also help forecast future demands. The data can be used to optimize applications in real-time without having the end-users feel any impact.

Cost management: From optimizing workloads to computational resources, SREs can and should find ways to save on VM, GPU, cloud and inferencing costs through observability.

Observability is crucial for organizations to address AI app sprawl and overcome myriad challenges that come along with it, especially as generative AI becomes a mainstay across enterprises. By following observability best practices and deploying the right automated tools, organizations can proactively identify and resolve issues and ensure all AI applications are always available and friction-free.

Bill Lobig is VP, Automation Product Management, IBM Software

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