IBM Instana Observability PayPerUse (with 14-day free trial)

What do you like best about the product?

I use IBM Instana for real-time application performance monitoring across our applications and infrastructure. It helps me track service dependencies, analyze distributed traces, identify performance bottlenecks, and investigate incidents more quickly. What I like most about IBM Instana is the level of automatic visibility it provides with relatively little manual configuration. The automatic discovery of applications, services, infrastructure, and their dependencies is especially valuable, as it quickly builds a clear picture of how the environment is connected. I also appreciate the combination of real-time monitoring, distributed tracing, and infrastructure metrics in one interface. This makes it easier to move from a high-level alert to the specific service, request, or infrastructure component causing the issue. The visual service maps and detailed transaction traces stand out because they make complex microservices environments much easier to understand and troubleshoot. The initial setup was very easy, taking just one day.

What do you dislike about the product?

The main area that could be improved is the initial learning curve. Instana provides a large amount of data, but the interface can feel quite dense when you first start using it, especially when navigating between services, traces, infrastructure metrics, and incidents. It was not always immediately clear which view was best for a particular task, such as investigating a slow transaction, checking infrastructure health, or understanding the dependencies between services.

What problems is the product solving and how is that benefiting you?

I use IBM Instana for real-time application performance monitoring, reducing investigation time, identifying bottlenecks faster, and understanding issue impacts across our environment. It solves problems with limited visibility in complex applications by connecting traces, metrics, and dependencies.

What do you like best about the product?

Developers spend up to 90% less time troubleshooting because the platform automatically pinpoints the root cause.

What do you dislike about the product?

It’s a bit pricey and feels overly complex for small teams.

What problems is the product solving and how is that benefiting you?

IBM Instana is a powerful, AI-driven observability platform that addresses one of the biggest challenges in modern software engineering: achieving real-time, full-stack visibility into complex microservices environments with minimal manual effort. Its auto-instrumentation and 1-second monitoring granularity help surface performance issues immediately, and its automated root cause analysis removes the tedious, hours-long work of manually correlating logs, metrics, and traces. Teams benefit from unified visibility across infrastructure, applications, and real-user experience—all in a single pane of glass—which can reduce alert fatigue and speed up incident resolution. Real-world users report up to a 90% reduction in troubleshooting time and up to 60% fewer revenue-impacting production incidents, making it a compelling ROI investment for DevOps and SRE teams. That said, pricing can be a barrier for smaller teams, and the initial setup comes with a learning curve. Even so, Instana’s automation-first approach makes it one of the most capable and efficient observability tools for Kubernetes-native, high-velocity engineering environments today.

What do you like best about the product?

I am using IBM Instana for infrastructure monitoring to ensure uptime and performance. I like that IBM Instana automates zero configuration monitoring and maps the entire infrastructure and application stack, which makes it an intelligent and effortless observability platform. The initial setup was quite easy.

What do you dislike about the product?

The pricing is high, and the dashboard and monitoring part is limited.

What problems is the product solving and how is that benefiting you?

I use IBM Instana for infrastructure monitoring, ensuring uptime and performance. It automates zero configuration monitoring, maps the entire infrastructure and application stack, and makes an intelligent and effortless observability platform available.

What do you like best about the product?

What I like best is the 'zero-effort' automation. Unlike other APM tools where you spend weeks configuring thresholds, Instana’s AutoTrace and discovery mapped our entire microservices architecture in minutes. The 1-second granularity provides a level of real-time visibility that makes catching intermittent spikes much easier than the standard 10-second averages.

What do you dislike about the product?

The UI can feel a bit heavy and occasionally sluggish when loading very large, complex dependency maps. Because it collects so much data, the initial learning curve is steep for junior engineers. The dashboarding is powerful, but customizing specific views can be less intuitive than I’d like sometimes there are so many menus that it’s easy to get lost when trying to find a specific obscure metric.

What problems is the product solving and how is that benefiting you?

It solves the complexity of monitoring microservices. It benefits me by providing a single source of truth for Dev and Ops, reducing our MTTR and saving hours of manual debugging every week.

What do you like best about the product?

How it turns highly technical system performance into clear, data-backed stories we can use, whether that’s for press releases, analyst briefings, or thought leadership. Instead of vague claims, it gives us real-time metrics and visualizations that make our messaging more credible, specific, and compelling.

What do you dislike about the product?

From a PR perspective, IBM Instana Observability can be a bit too technical out of the box, there’s still a heavy lift to translate raw telemetry into clear, media-ready narratives without relying on engineering.

What problems is the product solving and how is that benefiting you?

It translates complex language into clearer, more credible messaging, we’re not guessing or relying on vague inputs from engineering. Instead, we can speak to performance, reliability, and impact with real data, respond faster during incidents, and build stronger narratives backed by measurable outcomes.