Technical Manager at a consultancy with 1-10 employees
Reseller
Top 10
Jan 5, 2026
I usually recommend IBM Instana Observability for companies in the academic environment, as I have been working in a consultancy company for the last three years, where one of our customers built teaching environments with many connections. I cannot remember the name, but it is in the academic space. Additionally, I have presented the features and characteristics of IBM Instana Observability to many customers here in Spain, including BBVA, Consum, a retail company, and Telefónica. My role involved presentations and proof of concepts rather than installation and operation. With the academic-oriented company, I solved some problems related to installation, configuration, and recommendations. Using IBM Instana Observability for non-distributed applications does not seem sensible because if an application is housed on a single server, it falls under traditional monitoring systems where you simply check CPU, storage, I/O, and memory. For that, you do not need IBM Instana Observability. The real strength of IBM Instana Observability lies in observing distributed applications, identifying where failures happen across services interconnected on multiple servers.
Technical Lead at a tech services company with 11-50 employees
Real User
Top 10
Jan 5, 2026
I typically use IBM Instana Observability to monitor infrastructure and application. IBM Instana Observability shows what the issue is, what the incident is, and what the problem is. For example, it can identify if a server is at almost full storage capacity or if a Kubernetes cluster service is going down. I use IBM Instana Observability for health checks, such as uptime service monitoring. IBM Instana Observability has synthetic monitoring capabilities that check if an endpoint is still up or going down and display the latency.
My main use case for IBM Instana Observability is to gain more insights about my infrastructure, servers, traffic flow, CPU and memory utilization, and metrics. I use IBM Instana Observability to mainly understand the flow of traffic inside my Kubernetes clusters and to check the logs of my pods. On a daily basis, I use IBM Instana Observability mostly for the monitoring of my infrastructure stack.
I use IBM Instana Observability to trace our services, especially the incidents part and events. One particular feature I appreciate is the filtering of calls so that I can view analytics, including how many calls we received, how many failed, and how many succeeded.
Before IBM, I ordered our company's engineer to have a look at the tool and test it. I think it was two years ago, the transfer to IBM happened in our company. At the beginning, IBM Instana Observability did not work on IBM WebSphere and IBM DB2/400. It was only for monitoring the web application server, but now it can monitor. The tool is used for web application monitoring and database monitoring. IBM's Raspberry monitoring tool, which is locally made, is called Juniper. Juniper only monitors WaaS. Most of the customers are moving to containers or want monitoring of the database. IBM customers think about database monitoring and web application monitoring, including any other database and any other web application server monitoring. Nowadays, the solutions are separate, but customers think about one-vendor solutions.
IBM Instana Observability offers real-time application monitoring and management, designed for automation and intelligence on modern cloud-based environments. IBM Instana Observability provides deep visibility into application performance, empowering businesses with automated root cause analysis and intelligent alerts to optimize cloud-native applications. It captures and visualizes comprehensive health metrics to enhance operational efficiency across distributed systems, making it an...
I usually recommend IBM Instana Observability for companies in the academic environment, as I have been working in a consultancy company for the last three years, where one of our customers built teaching environments with many connections. I cannot remember the name, but it is in the academic space. Additionally, I have presented the features and characteristics of IBM Instana Observability to many customers here in Spain, including BBVA, Consum, a retail company, and Telefónica. My role involved presentations and proof of concepts rather than installation and operation. With the academic-oriented company, I solved some problems related to installation, configuration, and recommendations. Using IBM Instana Observability for non-distributed applications does not seem sensible because if an application is housed on a single server, it falls under traditional monitoring systems where you simply check CPU, storage, I/O, and memory. For that, you do not need IBM Instana Observability. The real strength of IBM Instana Observability lies in observing distributed applications, identifying where failures happen across services interconnected on multiple servers.
I typically use IBM Instana Observability to monitor infrastructure and application. IBM Instana Observability shows what the issue is, what the incident is, and what the problem is. For example, it can identify if a server is at almost full storage capacity or if a Kubernetes cluster service is going down. I use IBM Instana Observability for health checks, such as uptime service monitoring. IBM Instana Observability has synthetic monitoring capabilities that check if an endpoint is still up or going down and display the latency.
My main use case for IBM Instana Observability is to gain more insights about my infrastructure, servers, traffic flow, CPU and memory utilization, and metrics. I use IBM Instana Observability to mainly understand the flow of traffic inside my Kubernetes clusters and to check the logs of my pods. On a daily basis, I use IBM Instana Observability mostly for the monitoring of my infrastructure stack.
I use IBM Instana Observability to trace our services, especially the incidents part and events. One particular feature I appreciate is the filtering of calls so that I can view analytics, including how many calls we received, how many failed, and how many succeeded.
Before IBM, I ordered our company's engineer to have a look at the tool and test it. I think it was two years ago, the transfer to IBM happened in our company. At the beginning, IBM Instana Observability did not work on IBM WebSphere and IBM DB2/400. It was only for monitoring the web application server, but now it can monitor. The tool is used for web application monitoring and database monitoring. IBM's Raspberry monitoring tool, which is locally made, is called Juniper. Juniper only monitors WaaS. Most of the customers are moving to containers or want monitoring of the database. IBM customers think about database monitoring and web application monitoring, including any other database and any other web application server monitoring. Nowadays, the solutions are separate, but customers think about one-vendor solutions.
The solution is mainly used for observability and application performance management.