Unified Monitoring with Real-Time Precision
What do you like best about the product?
I really appreciate IBM Instana's dynamic graph and automatic discovery capabilities. These features eliminate the exhaustive manual configuration and constant tagging required by other enterprise tools, as Instana maps out the dependencies on its own. The one-second granularity is a game-changer as it allows us to pinpoint every single cell to a service and endpoint without needing custom instruction code. This feature has completely transformed how we handle distributed tracing across all microservices. I also love how easy the initial setup was for us, and I'd rate it a nine out of 10 for recommendation.
What do you dislike about the product?
While automated features are world-class, the performance does fall a bit short when it comes to long-term historical data retention and deep trend analysis. It is built for now, but looking back over several months of data to find very subtle patterns can be restrictive. I also feel like the native dashboard could be more flexible. While the APIs for reporting are solid, the out-of-the-box visualization options sometimes feel a bit rigid when you are trying to build a single pane of glass for non-technical stakeholders.
What problems is the product solving and how is that benefiting you?
IBM Instana solved our monitoring data fragmentation issue. It unified our monitoring, drastically reducing MTTR by automatically correlating events across layers, eliminating manual labor to understand database latency impacts on user journeys.
Indispensable for Financial Service Monitoring, Needs Improved Documentation
What do you like best about the product?
In my opinion, the most valuable capacity of IBM Instana is the sheer level of granular detail provided for each component in the flow. I find the automated dependency mapping indispensable. I also appreciate that the initial setup was not a burden for us; it was quite good and easy.
What do you dislike about the product?
I find the configuration and documentation process could use some improvement. Sometimes when we try to set up monitoring for newer or highly specific technology, the online documentation or step-by-step procedures aren't fully updated with the latest agent version. This leads to a bit of trial and error that could be avoided with a more synchronized release cycle. Also, while the UI is intuitive, some of the advanced filter options are tucked away in menus that aren't immediately obvious for a new user, creating a slight learning curve for the unmounted analytic side of the tool.
What problems is the product solving and how is that benefiting you?
I find IBM Instana solves the problem of ambiguity in distributed failures. It provides instant clarity on failure points, reducing time spent piecing log files together and increasing operational efficiency.
Streamlined Incident Management with Instana
What do you like best about the product?
I really like the correlation and tracing capabilities in IBM Instana, which are critical for my team. The way it visualizes calls and sub-calls for the entire system is top-notch. I can look at a specific trace and immediately see the health of the underlying host. It's incredibly useful for quickly understanding complex service interactions even when I'm overseeing services I'm not familiar with, thanks to the automated dependencies feature. This helps us achieve a rapid mean time to resolution, which is crucial for managing high-pressure demands.
What do you dislike about the product?
Yeah. It is a log ingestion process. Currently, the platform relies heavily on OpenTelemetry for logging, which can be required to, to worsen to set up and maintain compared to, compared to the magic of its automatic tracing sensors.
What problems is the product solving and how is that benefiting you?
I deploy IBM Instana to manage high-pressure demands and use it as a foundation for root cause analysis. It helps trace incidents, monitor services, identify bottlenecks, and resolve latency issues efficiently, reducing finger-pointing during system failures.
Powerful Monitoring with Room for Simplicity
What do you like best about the product?
I find IBM Instana's reporting and alerting system great. It allows me to set up jobs that send reports straight to our team, which makes our weekly reviews much easier. I also appreciate how easily it integrates with our existing database setup. That's how the alerting system works.
What do you dislike about the product?
It can be pretty complex to set up initially, especially if you are not a deep level engineer. The data consumption is also high and sometimes I find myself wading through too much information to find the one critical issue I actually need to fix.
What problems is the product solving and how is that benefiting you?
I use IBM Instana to monitor client websites, manage migrations, and handle major deployments. It alerts me if any issues arise, removing the need for manual checks. This helps me address problems quickly, focusing on actual incident resolution, while making weekly reviews smoother.
Intuitive Monitoring but Needs Better Third-Party Integration
What do you like best about the product?
Without a doubt, the module analysis and automatic ingestion are the most valuable capabilities for us. Instana's enterprise-wide infrastructure monitoring consolidates high-priority systems into one dashboard, making it easier to conduct system operations analysis without having to toggle between different vendors and consoles. This helps track the health and throughput of multiple IBM products effectively. Moreover, the setup was quite easy, which was a relief.
What do you dislike about the product?
If I had to point out the area of improvement, the integration with non-IBM products can feel a bit restrictive compared to its seamless support for the IBM ecosystem. When we try to bring in third-party or custom black box applications, the setup requires more manual heavy lifting than the plug-and-play experience we get with native IBM tools. Additionally, the notification system can be a bit overwhelming if you don't spend a significant amount of time fine-tuning your alert threshold and smart alerts. You can quickly find yourself dealing with a noisy volume of warnings that aren't all machine critical, which can lead to alert fatigue for on-call technicians.
What problems is the product solving and how is that benefiting you?
I use IBM Instana as a central dashboard for enterprise-wide monitoring, solving fragmented visibility issues and reducing delays in identifying bottlenecks. It consolidates system operations analysis by not needing to toggle between different vendors and consoles.
AI-Driven Monitoring with Room for Improvement
What do you like best about the product?
I really like the AI-based smart alerts in IBM Instana; they stand out for me. These alerts aren't just based on basic thresholds; they actually learn what normal looks like for our application, which helps us stay proactive rather than just reacting to crashes after they happen. Also, I found the initial setup to be pretty short and straightforward since it didn't need much to ask for.
What do you dislike about the product?
Sometimes, the AI gets a bit too confident and throws a false positive alarm. It can be a bit disruptive if you haven't spent the time to tune it properly.
What problems is the product solving and how is that benefiting you?
I use IBM Instana for health checks and time monitoring on customer-facing APIs. It cuts down the meantime to repair significantly by correlating events, pinpointing root causes, and letting us proactively fix issues before support tickets come in
Real-Time Insights with Room for UI Improvement
What do you like best about the product?
I really find the one-second metric granularity incredible. It makes a big difference in how I monitor services effectively. IBM Instana helps me see exactly how requests flow in real time, which is essential when dealing with multiple moving parts. It's also helpful that it maps dependencies automatically, so when there's a request lag, I can pinpoint the exact database call causing the issue.
What do you dislike about the product?
The UI can get pretty sluggish when trying to load a service map with a lot of nodes. It feels heavy. I also wish the alerting was a bit smarter out of the box, as sometimes it can get noisy during minor harmless spikes.
What problems is the product solving and how is that benefiting you?
I use IBM Instana to monitor services in real-time, mapping dependencies automatically to pinpoint bottlenecks when there's a slowdown. The one-second metric granularity is incredible, allowing me to identify the exact database call causing issues.
Observability has improved collaboration and predicts failures across distributed services
What is our primary use case?
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.
What is most valuable?
The impact of IBM Instana Observability on collaboration between development and operations teams is essential because it allows operations to identify incidents before they occur. This capability impresses customers greatly because operations have wide visibility and can pinpoint exactly where issues arise in the system.
This aspect creates a little pressure on development teams because operations can now predict system failures. They used to know when the system was failing, but with IBM Instana Observability, they can see potential failures beforehand.
This advantage enables them to swiftly identify breaking points in the system, communicate effectively with the development team, and enhance overall effectiveness rather than waiting until problems arise.
What needs improvement?
From my perspective, IBM Instana Observability is quite technical. Compared to some competitors, it offers an abundance of information about system performance but lacks planning or capacity planning information. You do not receive reports with recommendations; instead, it provides only the technical layer.
Other companies, like Compuware, give more functional information about your environment, while IBM Instana Observability provides only limited functional insights. This means you often must interpret the data independently. Unlike other tools that can offer recommendations to save resources or costs, IBM Instana Observability does not provide that functionality.
On the bright side, it is much more affordable than some other options, but it isn't complete. If you want full functionality with IBM Instana Observability, you also need to acquire other products for additional insights in monitoring areas, such as networking monitoring tools or similar products. For instance, we often recommend Turbonomic, which provides complementary insights.
One potential feature that could improve IBM Instana Observability is the ability to translate KPIs into monetary terms. It would be interesting to have a product that integrates IBM Instana Observability with Turbonomic, as Turbonomic can utilize data from IBM Instana Observability to inform you about unnecessary spending and suggest whether you can consolidate servers or optimize containers for quicker response times. Implementing some level of simulation or capacity planning would greatly enhance the current capabilities of IBM Instana Observability.
For how long have I used the solution?
I have been dealing with IBM Instana Observability for the most two years; it is not a new product, but it is a new addition to the IBM portfolio since IBM purchased it three or four years ago.
How are customer service and support?
In general, we did have experiences where a significant issue arose during implementation, often involving compatibility problems with JavaScript libraries used by IBM Instana Observability. When that happens, I report it to IBM, and since I still have contacts there, it is easy for me to follow up on incidents.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I did not remember that Dynatrace is the tool from Compuware until now. Dynatrace is much more comprehensive, and when I visited some customers, they mentioned that while IBM Instana Observability works adequately, they already have Dynatrace, which provides extensive monitoring and a wealth of information, along with recommendations and various functional parameters. However, Dynatrace is also considerably more expensive.
How was the initial setup?
The installation does not take too much time because it operates on the cloud. However, it depends on what you need to observe or monitor. What I do is provide recommendations to customers and solve problems, most of which relate to the user interface. IBM Instana Observability works quite well, especially for monitoring containers and Kubernetes environments.
What was our ROI?
The most significant metric I track to assess IBM Instana Observability's effectiveness in reducing mean time to resolution is time. You always want your systems to respond promptly. Another critical metric is cost; IBM Instana Observability can highlight when there are too many or too few resources allocated for a task. For example, in a Kubernetes environment with containers, it is important to investigate whether more resources or containers are used than necessary. After adjusting the system for optimal resource allocation, the focus shifts back to measuring time, as I aim for the best response times with the fewest resources.
What's my experience with pricing, setup cost, and licensing?
I would evaluate the implementation process of IBM Instana Observability as not complex at all because you pay the license, and IBM takes care of everything. The only problem we occasionally face, due to its nature as a cloud product, is that the monitoring environment or operating system you use can sometimes lead to issues with the user interface or with specific KPIs you want to see.
What other advice do I have?
I know IBM products because I have been working for IBM for 18 years, so I am familiar with them, but obviously, it is very difficult to know each product. In the monitoring area, now called observability, I know IBM Instana Observability and IBM SevOne because they are part of the observability portfolio, but I have not been working with these products intensively. However, I can learn fast because I have been working for such a long time at IBM, learning new products and portfolios every year.
The key is knowing how to interpret the performance metrics and responding accordingly.
To be honest, I have not used IBM Instana Observability's automated discovery feature. That is a functionality that comes by default as I understand it, so when you activate it, you see all the elements in your environment, but as I mentioned earlier, I am not an expert in all the features of IBM Instana Observability.
As for the insights gained from IBM Instana Observability's AI-powered analytics for predicting potential application disruptions, I do not have much to say because the installations I managed have been quite straightforward. We monitored several servers, some containers, and cloud services, but the service portfolio we monitored was relatively simple. From my understanding, the AI is already embedded in IBM Instana Observability, so you do not need to do much more.
I would rate this product an 8.5 overall.
Monitoring has reduced incident resolution time and provides rapid root cause visibility
What is our primary use case?
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.
What is most valuable?
In my experience, the best features IBM Instana Observability offers are the APM trace. I believe it is the best option because you install one agent and IBM Instana Observability has a discovery agent to find the other services inside the server. I have tried DataDog and Signals, and IBM Instana Observability is superior.
The tracing feature of IBM Instana Observability stands out for me because the dashboard and UI are easy to view. You can see which service has a problem, what the point of slowness is, where it is slow, and what the root cause is. For example, the dashboard can identify that a database query is slow.
IBM Instana Observability has had a very positive impact on my organization because it shortens the time required to find the root cause when we have a problem. IBM Instana Observability pinpoints the exact issue. With multiple servers and multiple applications, IBM Instana Observability allows us to resolve issues very quickly because we immediately know that a disk is full, the storage is full, or the database is down. I think we can resolve issues in one hour.
The newest feature I saw in IBM Instana Observability is the integration with IBM Console to check for vulnerabilities, and it integrates generative AI. IBM Instana Observability checks the cost for using the AI, including how many tokens are used.
What needs improvement?
IBM Instana Observability can be improved because the current software is quite large with many components in a single software package. If you need to install the IBM Instana Observability core backend, it uses a large scale. An improvement would be to reduce the capacity required for installation.
The pricing for IBM Instana Observability is something I would address in terms of needed improvements because it is expensive. I understand it is easy and good to use, but I think it is expensive for a small to medium-sized enterprise to use.
For how long have I used the solution?
I have been using IBM Instana Observability for two years.
What do I think about the stability of the solution?
IBM Instana Observability is stable.
What do I think about the scalability of the solution?
IBM Instana Observability's scalability is good because the platform uses containers, which makes it scalable.
How are customer service and support?
IBM Instana Observability has ticket support available.
How would you rate customer service and support?
What was our ROI?
I have seen a return on investment with IBM Instana Observability, particularly in the time saved. IBM Instana Observability can quickly reduce the time to resolve problems from one day to one hour.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing for IBM Instana Observability shows it is expensive for the pricing and licensing. IBM Instana Observability counts per server, which they call MVS.
Which other solutions did I evaluate?
Before choosing IBM Instana Observability, I evaluated other options including DataDog.
Business monitoring has pinpointed slow code and queries and now solves recurring client issues
What is our primary use case?
My main use case for IBM Instana Observability is running agents on a host to monitor infrastructure and applications.
I have a specific example of how I use IBM Instana Observability to monitor my infrastructure. When I installed IBM Instana Observability backend, I installed some IBM Instana Observability agents on the VMs that were going to be monitored and then I followed the monitoring on the infrastructure tab on the IBM Instana Observability backend.
What is most valuable?
The best features IBM Instana Observability offers are business monitoring by far.
I can tell you more about what I appreciate about the business monitoring capabilities. It can go deeper into the application, especially because we are using a lot of IBM BAW software, and it has helped us identify what code in the application or what query is taking a long time or consuming resources incorrectly.
Custom dashboards are also a good feature because we can customize them to our needs and we can discuss them with clients to better demonstrate how IBM Instana Observability works and helps them.
IBM Instana Observability has positively impacted our organization because it has helped us solve many problems and sell some products. For example, a client had a problem recurring every Thursday, and they did not know what the problem was. When we installed IBM Instana Observability and got it running, we easily monitored and found what was causing the issue on that specific day.
What needs improvement?
I think it would be great if IBM Instana Observability stayed focused on on-premise environments because not every client has implemented cloud environments and infrastructure yet.
For how long have I used the solution?
I have been using IBM Instana Observability for about two years now.
What do I think about the stability of the solution?
IBM Instana Observability is stable.
What do I think about the scalability of the solution?
Its scalability is very good, but I am not certain what you mean by scalability.
I did not have any challenges because the IBM documentation is well explained and we can use that documentation for scalability purposes. We did not have many problems.
How are customer service and support?
Customer support is good; sometimes it cannot go as deep as I expected, but overall it is good.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I did not previously use a different solution; IBM Instana Observability was the first one that we used.
How was the initial setup?
I did not evaluate other options because we are clients with IBM and we are premium partners, and this solution was the best for us by all means.
What about the implementation team?
I think we are some kind of premium partners with this vendor.
What's my experience with pricing, setup cost, and licensing?
I think the pricing is good and I do not think it is high. The bundle when you need to buy another 10 licenses for host agents and for VMware agents is good because we can monitor and see IBM Instana Observability functionality. You can see IBM Instana Observability backend functionalities immediately because when you have 10 licenses, you for sure have 10 VMs where you can monitor or you can set up the agent.
What other advice do I have?
My advice to others looking into using IBM Instana Observability is to use it. Do not worry or take second guesses; it is a good platform. I would rate this review an 8 out of 10.
