Bringing IBM i Into the Modern Observability Stack: The Missing Piece of Enterprise AIOps

Slawomir Michalik
Omnilogy

In the ever-evolving digital landscape, enterprises are increasingly focused on enhancing their observability stacks to gain deeper insights into their IT environments. Observability has become a cornerstone of modern IT operations, enabling organizations to monitor, diagnose, and optimize their systems with unprecedented precision. However, a critical piece of the puzzle often goes unnoticed in this transformation: IBM i.

The Legacy and Importance of IBM i

IBM i, formerly known as AS/400, may be considered a legacy system, but it is far from obsolete. It powers a significant portion of the world's critical business applications, especially in industries such as banking, manufacturing, and retail. IBM i systems are renowned for their robustness, reliability, and security. They manage enormous amounts of business logic that are fundamental to enterprise operations. Despite their importance, these systems remain largely invisible to modern observability platforms.

In many organizations, IBM i operates as the "dark matter" of enterprise infrastructure. It is vital yet often hidden from the spotlight, running seamlessly behind the scenes. This invisibility poses a challenge for CIOs and IT leaders aiming to create a comprehensive observability stack, as the lack of visibility into IBM i systems can lead to blind spots in monitoring and diagnostics.

The Gap in Modern Observability Platforms

Modern observability platforms are designed to provide granular insights into cloud-native architectures. They excel at monitoring microservices, containers, and distributed systems. However, they often fall short when it comes to traditional systems like IBM i. This gap can have significant implications for enterprises that rely on these systems for mission-critical operations.

Without integration into the observability stack, IBM i systems can become points of failure that are difficult to detect and diagnose. When issues arise, the delay in identifying and resolving them can lead to costly downtime and impact business operations. As enterprises transition to AI-driven operations (AIOps), the need for comprehensive visibility across all systems becomes even more pronounced.

Bridging the Gap: Integrating IBM i into the Observability Stack

To address this challenge, organizations must consider integrating IBM i into their observability ecosystems. This integration requires a thoughtful approach and the deployment of specialized tools that can capture telemetry data from IBM i systems and feed it into modern observability platforms.

Integrating IBM i into observability platforms can be achieved through middleware solutions, which act as bridges between IBM i and observability platforms. These solutions convert signals from IBM i systems into logs, metrics, and traces understandable by observability platforms. APIs and connectors offered by many modern observability tools make it possible to incorporate critical metrics from IBM i in the overall observability stack. Additionally, partnering with specialized vendors is an effective strategy. These vendors specialize in IBM i integration and offer tailored solutions to enhance visibility, providing tools and services specifically designed to monitor IBM i systems and integrate them seamlessly into existing observability stacks.

Benefits of a Unified Observability Strategy

By bringing IBM i into the fold of the observability stack, CIOs and IT leaders can unlock several benefits:

  • Holistic Visibility: Integrating IBM i with modern observability platforms provides a unified view of the entire IT environment, reducing blind spots and enabling comprehensive monitoring.
  • Proactive Issue Resolution: Enhanced visibility allows organizations to detect anomalies early, leading to quicker diagnostics and proactive issue resolution, minimizing downtime and its associated costs.
  • Improved AIOps Capabilities: A unified observability strategy enhances the effectiveness of AIOps by providing the necessary data to drive intelligent automation and decision-making.
  • Operational Efficiency: With a complete picture of the IT landscape, organizations can optimize performance, allocate resources more effectively, and improve overall operational efficiency.

As enterprises continue to modernize their IT operations, the integration of IBM i into the observability stack is no longer optional — it is essential. Recognizing IBM i as a vital component of the enterprise infrastructure and making it visible within modern observability platforms will empower organizations to achieve a truly comprehensive and effective AIOps strategy.

For CIOs and IT leaders, the path forward involves bridging the gap between legacy systems and modern observability tools, ensuring that IBM i is no longer the "dark matter" but a visible and manageable part of the IT ecosystem. By doing so, enterprises can harness the full potential of their technology investments, driving innovation and maintaining their competitive edge in an increasingly digital world.

Slawomir Michalik is VP at Omnilogy

Related Links

Hot Topics

The Latest

When the Database Is the Problem, Is APM Enough?

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

From Cleanup to Prevention: The Future of Cloud-Native Cost Optimization

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

The Real Enterprise AI Risk Isn't Hallucinations

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

Beyond Buy vs. Build: The New Playbook for Data Pipelines

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

The Corporate Network Is Fading - Here's What Replaces It

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

IT Leaders Must Establish a Network Data Architecture Practice

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

Data Center Outages Are Decreasing but More Costly

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

Observability Has a Physical Layer Now: What AI Infrastructure Teaches IT Operations

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

TLS Certificate Expiration Is Becoming an Observability Problem

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprise Cloud Observability: Choosing the Right Starting Point

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...

Bringing IBM i Into the Modern Observability Stack: The Missing Piece of Enterprise AIOps

Slawomir Michalik
Omnilogy

In the ever-evolving digital landscape, enterprises are increasingly focused on enhancing their observability stacks to gain deeper insights into their IT environments. Observability has become a cornerstone of modern IT operations, enabling organizations to monitor, diagnose, and optimize their systems with unprecedented precision. However, a critical piece of the puzzle often goes unnoticed in this transformation: IBM i.

The Legacy and Importance of IBM i

IBM i, formerly known as AS/400, may be considered a legacy system, but it is far from obsolete. It powers a significant portion of the world's critical business applications, especially in industries such as banking, manufacturing, and retail. IBM i systems are renowned for their robustness, reliability, and security. They manage enormous amounts of business logic that are fundamental to enterprise operations. Despite their importance, these systems remain largely invisible to modern observability platforms.

In many organizations, IBM i operates as the "dark matter" of enterprise infrastructure. It is vital yet often hidden from the spotlight, running seamlessly behind the scenes. This invisibility poses a challenge for CIOs and IT leaders aiming to create a comprehensive observability stack, as the lack of visibility into IBM i systems can lead to blind spots in monitoring and diagnostics.

The Gap in Modern Observability Platforms

Modern observability platforms are designed to provide granular insights into cloud-native architectures. They excel at monitoring microservices, containers, and distributed systems. However, they often fall short when it comes to traditional systems like IBM i. This gap can have significant implications for enterprises that rely on these systems for mission-critical operations.

Without integration into the observability stack, IBM i systems can become points of failure that are difficult to detect and diagnose. When issues arise, the delay in identifying and resolving them can lead to costly downtime and impact business operations. As enterprises transition to AI-driven operations (AIOps), the need for comprehensive visibility across all systems becomes even more pronounced.

Bridging the Gap: Integrating IBM i into the Observability Stack

To address this challenge, organizations must consider integrating IBM i into their observability ecosystems. This integration requires a thoughtful approach and the deployment of specialized tools that can capture telemetry data from IBM i systems and feed it into modern observability platforms.

Integrating IBM i into observability platforms can be achieved through middleware solutions, which act as bridges between IBM i and observability platforms. These solutions convert signals from IBM i systems into logs, metrics, and traces understandable by observability platforms. APIs and connectors offered by many modern observability tools make it possible to incorporate critical metrics from IBM i in the overall observability stack. Additionally, partnering with specialized vendors is an effective strategy. These vendors specialize in IBM i integration and offer tailored solutions to enhance visibility, providing tools and services specifically designed to monitor IBM i systems and integrate them seamlessly into existing observability stacks.

Benefits of a Unified Observability Strategy

By bringing IBM i into the fold of the observability stack, CIOs and IT leaders can unlock several benefits:

  • Holistic Visibility: Integrating IBM i with modern observability platforms provides a unified view of the entire IT environment, reducing blind spots and enabling comprehensive monitoring.
  • Proactive Issue Resolution: Enhanced visibility allows organizations to detect anomalies early, leading to quicker diagnostics and proactive issue resolution, minimizing downtime and its associated costs.
  • Improved AIOps Capabilities: A unified observability strategy enhances the effectiveness of AIOps by providing the necessary data to drive intelligent automation and decision-making.
  • Operational Efficiency: With a complete picture of the IT landscape, organizations can optimize performance, allocate resources more effectively, and improve overall operational efficiency.

As enterprises continue to modernize their IT operations, the integration of IBM i into the observability stack is no longer optional — it is essential. Recognizing IBM i as a vital component of the enterprise infrastructure and making it visible within modern observability platforms will empower organizations to achieve a truly comprehensive and effective AIOps strategy.

For CIOs and IT leaders, the path forward involves bridging the gap between legacy systems and modern observability tools, ensuring that IBM i is no longer the "dark matter" but a visible and manageable part of the IT ecosystem. By doing so, enterprises can harness the full potential of their technology investments, driving innovation and maintaining their competitive edge in an increasingly digital world.

Slawomir Michalik is VP at Omnilogy

Related Links

Hot Topics

The Latest

When the Database Is the Problem, Is APM Enough?

Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...

From Cleanup to Prevention: The Future of Cloud-Native Cost Optimization

Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...

The Real Enterprise AI Risk Isn't Hallucinations

Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...

Beyond Buy vs. Build: The New Playbook for Data Pipelines

While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...

The Corporate Network Is Fading - Here's What Replaces It

For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...

IT Leaders Must Establish a Network Data Architecture Practice

As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...

Data Center Outages Are Decreasing but More Costly

The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...

Observability Has a Physical Layer Now: What AI Infrastructure Teaches IT Operations

The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...

TLS Certificate Expiration Is Becoming an Observability Problem

Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...

Enterprise Cloud Observability: Choosing the Right Starting Point

Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...