The Tracing feature and to find root causes Review collected by and hosted on G2.com.
As far as I know you cannot have multiple mandants Review collected by and hosted on G2.com.
Generated from real user reviews
Last updated: Nov 04, 2026
| Time to go live | Relative frequency |
|---|---|
| Under 1 month | Common |
| 1–3 months | Common |
| 3–6 months | Also reported |
| 6–12 months or longer | Less frequent |
The Tracing feature and to find root causes Review collected by and hosted on G2.com.
As far as I know you cannot have multiple mandants Review collected by and hosted on G2.com.
We have just deployed Instana to non-prod environment and I like it so far because it can monitor HMC, VIOs, LPARs, and frames. It is easy to understand and I have been told it is easy to integrate as well. Review collected by and hosted on G2.com.
We spent a lot of time building the system. I wished it was much faster. Review collected by and hosted on G2.com.
I really like the agent deployment because it discovers services instantly without requiring us to do a lot of configuration. I also appreciate the alerting system; it has been a game changer for improving our incident response times. On top of that, the dynamic service maps help us derive actionable insights, which are essential for our application performance monitoring. Review collected by and hosted on G2.com.
It can take a significant amount of time and effort to train new users on its advanced functionality and full set of features. In my opinion, it’s also noticeably pricier than other APM tools I’ve worked with. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.
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. Review collected by and hosted on G2.com.

I like how easy it is to connect IBM Instana with our infrastructure. I also love the fact that they have a free trial, which was perfect for us. We used the 14-day free trial to decide if IBM Instana is the right fit for us, and then we switched to the pay-per-use plan, which we've been using for about 3 months. The free trial was invaluable, and it was great for figuring out if IBM Instana was suitable without actually making a monetary commitment. For the last 3-4 months, IBM Instana has worked perfectly for our use case. The initial setup was very straightforward. Review collected by and hosted on G2.com.
Nothing really. I enjoyed the entire experience so far (about 3-4 months). Review collected by and hosted on G2.com.
I find the most valuable aspect of IBM Instana to be its end-user experience monitoring and transaction tracing. It provides incredible clarity by allowing us to trace a single declined transaction from the front-end UI through our cloud APIs and databases. I also find the automatic anomaly detection promising, as it helps us spot spikes and decline rates before they become widespread issues. The tool's insights, clear visualizations, and its ability to communicate technical debt in terms of lost revenue to stakeholders are great for a team focused on both business outcomes and UX. The initial setup was notably smooth, and the auto-discovery began mapping our transaction flows almost immediately, providing actionable error patterns quickly. Review collected by and hosted on G2.com.
I haven't identified any major deal breakers or specific dislikes here. The platform is quite deep, so there is naturally a lot to take in during the initial pilot phase. We are still evaluating how well it integrates with some of our more niche business intelligence tools. Review collected by and hosted on G2.com.
The standout feature for me is the smart alert system combined with real-time data insights. I am particularly impressed by how the alerts are context-aware. They don't just tell me something is wrong; they give me the immediate visibility needed to take swift corrective action. Another huge win is the faster deployment capabilities. Because the platform uses an automated discovery model, we can roll out new services and have them fully monitored within minutes. This efficiency is a massive boost for our operations, especially during high-pressure release cycles where we don't have time for manual configuration. Review collected by and hosted on G2.com.
To be honest, I don't have any major complaints as of now. If I had to pick something for the product team to look at, I'd suggest making the initial landing page a bit more customizable so I can pin my most frequent service maps right to the front. While the documentation is great, some of the more advanced features like custom trace filtering can take a little bit of trial and error to master. However, these are minor nice to haves rather than actual deal breakers. As the core functionality is incredibly solid. And has lived up to our expectations. Review collected by and hosted on G2.com.
I find IBM Instana's automatic service discovery and topology map to be the most valuable capabilities for my team. In our environment, where services are constantly being updated or scaled, manual monitoring configuration is simply not an option. Instana's ability to automatically detect every new component, from containers to individual language runtimes, and instantly map their dependencies is a massive time saver. This zero-configuration visibility ensures that our monitoring is always as current as our code. Being able to see a high fidelity, end-to-end trace of a transaction across five different services without having to write a single line of instrumentation code is frankly a game changer for our productivity. The setup was remarkable, especially considering the scale of our deployment. We used the standard Kubernetes Helm Chart to push the agents across our clusters, and the discovery phase kicked in almost immediately. Within about fifteen to twenty minutes, we had a fully populated map of our infrastructure, and the platform essentially configured itself. Review collected by and hosted on G2.com.
While the automation is excellent, I do feel that the dashboard flexibility could be improved. When you're dealing with a large organization, different stakeholders need different views. And sometimes the standard widgets feel a bit too rigid for our specific reporting requirements. I've also noticed that the initial setup, while automated, still requires a fair amount of policy tuning to get the alerting just right for a large-scale environment. Otherwise, you can end up with a bit of noise during routine maintenance. Review collected by and hosted on G2.com.
I love using IBM Instana as it is our primary telemetry engine to oversee our production Kubernetes clusters, especially since we're pushing code multiple times a day across several different clusters. It's my go-to tool for distributed tracing, allowing me to follow individual user requests as they move from our front end through various middleware services into our databases. Instana provides a vital high fidelity map of how data is moving through the system in real-time. One aspect I appreciate is its ability to solve the needle in the haystack problem during production outages by using an automated dependency map, which transforms our debugging process into a more accurate and efficient approach. The most impressive part of the platform is the combination of automatic discovery and immediate tracing. I find the zero-effort visibility to be a lifesaver, especially when managing a dynamic environment where things are constantly scaling up and down. Being able to see a full end-to-end trace across a complex call path within seconds of a deployment is invaluable. The setup was probably the easiest part of the migration. We simply added the Instana agent to our Kubernetes demand sets, and within about fifteen minutes, it self-discovered our entire topology without any need for adding custom libraries or configurations. Review collected by and hosted on G2.com.
While the data is real-time, the UI sometimes feels like it's struggling to keep up. I'm trying to load a massive global service map with hundreds of nodes, the interface can feel heavy and slow to respond, which is frustrating when you're in the middle of a high priority incident. I also think the alerting engine needs a bit more intelligence out of the box. It can be quite noisy if a service has a tiny three-second CPU spike that resolves itself. Fine-tuning the smart alerts to ignore these transient jitters takes more manual effort than I'd like. And as others have noted, the pricing model is definitely on the premium side, making it a tough pill to swallow as we continue to scale our node count. Review collected by and hosted on G2.com.
I really value the auto discovery and zero touch instrumentation features of IBM Instana; they are easily the most valuable parts for me. With its single agent architecture, Instana captures everything the moment it's deployed, eliminating the need for manual wrapping of code or restarting services to obtain traces. The dynamic graph that updates in real time maps out service dependencies, containers, and hosts, which is great for a developer-focused workflow. I appreciate being able to view a full stack trace without spending days on configuration, which significantly boosts productivity. The setup experience was probably the smoothest I've had with an enterprise monitoring tool, virtually requiring no customization on the Kubernetes side to get the basic traces running, making the setup essentially plug and play. Review collected by and hosted on G2.com.
My biggest grievance is the pricing structure. It's based on a per host, per agent model, which becomes incredibly expensive very quickly as you scale up large Kubernetes clusters with high node counts. For a company running a lot of smaller, ephemeral instances, the costs can start to feel prohibitive compared to the value of the tool. Additionally, I find the initial UI layout to be a bit overwhelming for new users. There is a lot of data being thrown at you at once, and it takes a significant amount of click around time to figure out how to filter out the noise and get to the specific metrics that matter for a quick health check. Review collected by and hosted on G2.com.