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.
Find out what your peers are saying about IBM, Elastic, Grafana Labs and others in Application Performance Monitoring (APM) and Observability. Updated: November 2025.
Application Performance Monitoring (APM) and Observability help improve the efficiency of applications by providing visibility and insights into system performance.
Application Performance Monitoring and Observability involve tracking and analyzing the performance of applications and infrastructure. APM focuses on detecting and diagnosing performance issues, while Observability emphasizes gaining insight into the internal state of systems. By combining these approaches, IT teams can ensure...
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.