IBM Instana Observability Reviews

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

My main use case for IBM Instana Observability is to help with application performance monitoring. It helps me build understanding of my infrastructure use cases by showing which service belongs to which application and which services are dependent on which applications. It helps me get real-time monitoring of my infrastructure. I have used it to monitor IBM Power systems, VMware vSphere environments, and HMC. I have also used it to monitor the AWS cloud platform. It shows me a roadmap and indicates which services depend on other services.

The best features IBM Instana Observability offers include one-second granularity in that it goes down to specific services. For example, when my application is speaking to my database, it helps show me the particular services of the application and the specific services of the database that it is actually speaking to. It helps me build an observability map to show how traffic is flowing from the application down to the database and shows me each service component that is speaking to each other. Another key feature is its ability to build a live map, and it also shows real-time metrics and traces, the application response time, compute resources, and more.

The real-time metrics and observability map from IBM Instana Observability have helped me in my daily work. When I had to manually push the observability to see if I was trying to send real-time dumps to stress test my compute resource, there was a particular time I was trying to stress test it and it showed me that the particular resource was being affected as a result of the stress. IBM Instana Observability has impacted my organization positively in that it has helped me find out what the issue is in real-time because of its one-second granularity and its ability to identify issues as quickly as possible.

I have seen specific outcomes from IBM Instana Observability, such as help monitoring latency in microservices applications. It has helped me get real-time metrics around latency, IO disk utilization, network utilization, read-writes, bandwidth, and compute resources. It also provides traces for end-to-end request flow.

IBM Instana Observability can be improved by providing access to the materials. It is not open-source, and I have to be a partner to get more access to the products.

I have been using IBM Instana Observability for two years.

IBM Instana Observability is stable.

IBM Instana Observability's scalability is good in that I can still support more features and more container-based applications. When it started, it was basically more about on-premises services, but now I can use it to monitor container environments. More innovations are coming in every day, so it is scalable and more applications are becoming container-based.

The customer support I experience with IBM Instana Observability is great. IBM support for Instana is responsive and helpful.

Positive

I never used a different solution before.

I have seen a return on investment with IBM Instana Observability. Time saved is a relevant metric because it helps me identify issues quickly. Rather than having to log into every server to see what is wrong with it, once I have the agent installed in my infrastructure, I just need it on one box. From there I can draw in other servers or my virtualized environment. It provides a single pane of glass from which I can see what is happening with all the servers in my infrastructure, which saves time.

I do not have much experience with pricing, setup cost, and licensing. I only worked with the product.

I did not evaluate other options before choosing IBM Instana Observability.

My advice to others looking into using IBM Instana Observability is that it gives real-time and automated visibility into the application and infrastructure. It helps detect issues faster and helps fix them quickly. I rate this product 9 out of 10.

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.

One of the best features IBM Instana Observability offers is its nice and clean UI, with everything being clean and sorted out.

What stands out to me specifically about the UI of IBM Instana Observability is the way everything is organized, clean, easy to read, and easy to understand with clear navigation to each component.

IBM Instana Observability has positively impacted my organization by making it easy to observe the entire infrastructure under one platform, which was the biggest advantage of onboarding onto IBM Instana Observability.

Once we had an incident where my Kubernetes pods were crashing frequently, and it was really easy to troubleshoot because of the easily available monitoring tool IBM Instana Observability. It was easy to navigate inside IBM Instana Observability and find the logs from the pods and debug the traffic flow.

IBM Instana Observability definitely saves a lot of time. Since it integrates many things into one dashboard, it is really easy to navigate and find the root causes of failures, making it easy to troubleshoot issues as well, and all of this saves a lot of time.

One main issue I found with IBM Instana Observability was the customer support, which was very poor when we needed some features to be enabled or integrated into IBM Instana Observability sensors. They used to take a long time to respond and implement the features we requested, and customer support was not really great. They were slow to integrate new features, whereas competitors were providing better features at a faster pace.

IBM Instana Observability is not really stable; I would say it is stable approximately 95 percent of the time.

I have been using IBM Instana Observability for around two years.

The scalability of IBM Instana Observability is pretty good.

The customer support of IBM Instana Observability is really awful; that is one area where I found myself disliking IBM Instana Observability, as they are very slow to respond and integrate new features.

I would rate the customer support of IBM Instana Observability five out of ten.

Positive

Previously, I was using self-managed Prometheus, but then it was an organizational decision to move to a managed service, so we went with IBM Instana Observability.

I myself did not deploy IBM Instana Observability; the seniors and the leads in my team actually did that, so they would have more insight on that.

Before choosing IBM Instana Observability, I evaluated a few others such as DataDog and Groundcover.

IBM Instana Observability is not a top-of-the-line tool and definitely has flaws, but it also has a good side as well.

I would suggest others looking into using IBM Instana Observability to fully understand it first and see if it fits their use case. If their use case is very simple and beginner level, there is no need to go with a sophisticated tool such as IBM Instana Observability; but if they have a pretty large infrastructure, they can definitely go with IBM Instana Observability.

My company has no business relationship with IBM Instana Observability other than being a customer; it is purely that.

I would definitely suggest that the customer experience of IBM Instana Observability be improved significantly, and as far as the features go, please be quick to adopt new features into the tool, since competitors are really aggressive in implementing new features and rolling them out to users.

I rate IBM Instana Observability a seven out of ten.

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.

IBM Instana Observability sends alerts through Slack, and I check Slack for messages. When I review the messages, I find the link to a particular trace. When I view a particular trace, I can see where I had a failed connection, had an error, and so on.

The integration with alerting systems such as email and Slack is the best feature of IBM Instana Observability in my opinion. The alerting integrations in IBM Instana Observability are mostly reliable, though it depends on the filter I put. The problem is that the filter is somewhat complex to integrate.

IBM Instana Observability has positively impacted our organization by decreasing our 500 errors. Our errors in general have decreased, our response time has decreased, and so on.

The interface of IBM Instana Observability is really slow, especially when there is a lot of data and when there are a lot of traces. The interface almost hangs up.

The alerting integrations in IBM Instana Observability are mostly reliable, though it depends on the filter I put. The problem is that the filter is somewhat complex to integrate.

I had many false positives with IBM Instana Observability. Then I fixed the filters and it became more accurate on the errors reported. Also, errors gradually decreased from around 10 to 500 errors per 100 calls to one or two.

I have been using IBM Instana Observability since I joined Ejada, for about two years now.

IBM Instana Observability is stable.

IBM Instana Observability scales well.

I did not encounter customer support for IBM Instana Observability.

I did not previously use a different solution before IBM Instana Observability.

I have seen a return on investment with IBM Instana Observability, but we do not have really solid metrics. I can only say that we saved time, especially in the response time department. It made a notable difference from when we were almost blind to being able to respond to calls immediately.

My experience with pricing, setup cost, and licensing for IBM Instana Observability was fair. It is not that costly, especially since we only use two instances.

Before choosing IBM Instana Observability, we did not evaluate other options.

My advice to others looking into using IBM Instana Observability is to set up your alerts correctly to avoid false positives. I would rate this product 7 out of 10.

My main use case for IBM Instana Observability is for end-to-end monitoring from the application side, and also from the infrastructure and log monitoring.

For end-to-end monitoring in my work, I use IBM Instana Observability to monitor the transaction of application services and know the performance of the request latency and error rate. And for the infrastructure, I also monitor the utilization of CPU, memory, disk, and network.

The best features IBM Instana Observability offers right now include application monitoring and APM because they are very insightful for monitoring the performance of application services.

The application monitoring feature of IBM Instana Observability stands out for me because the analysis of the metrics and telemetry provides a lot of data, making it very helpful for the operational side.

IBM Instana Observability has positively impacted my organization because basically our company is in IT consulting, and our customers have a use case for monitoring, which creates a lot of demand for monitoring tools.

IBM Instana Observability can be improved by simplifying the installation process, reducing the number of manual steps and dependencies, especially for hybrid, on-premise environments.

I think the Instana team can improve the recommendation feature so that the tool is not only for identifying issues but can also give recommendations.

I have been using IBM Instana Observability for around one year, maybe six months.

IBM Instana Observability is stable.

IBM Instana Observability demonstrates scalability, especially in dynamic, distributed environments such as microservices and Kubernetes and can handle growth, service, and workload efficiently with minimal performance impact.

I think the customer support for IBM Instana Observability is good.

My experience with IBM Instana Observability's customer support has been very helpful and responsive because they have a minimum SLA to support us if we have a problem with IBM Instana Observability.

Positive

I have used DataDog and Dynatrace, not switching but using three observability tools.

If we are using IBM Instana Observability, we can save money because first, the pricing is very affordable. Second, if we have a monitoring tool, we can save our transactions and see the performance of the application using MTTR and MTTD. We can also use metrics such as request latency and error to know the performance of our application transactions.

I think the cost of IBM Instana Observability is cheaper.

I find the cost of IBM Instana Observability to be very affordable compared to competitors because the pricing mechanism is based on the host that we monitor, unlike other competitors such as DataDog and Dynatrace, whose pricing is based on other factors. IBM Instana Observability offers an all-in-one package that allows us to calculate with just one host for the hosts we want to monitor, including infrastructure, application, real-user monitoring, and logs.

Before choosing IBM Instana Observability, I evaluated Dynatrace as an option.

I think maybe our customers need IBM Instana Observability for monitoring the IBM platform, such as from AS/400 IBM.

I think for the error rate on the application side, using IBM Instana Observability helps our customers to know the root cause that triggers a failed request or transaction.

For others looking into using IBM Instana Observability, I would recommend that they consider adding a recommendation feature to IBM Instana Observability.

My additional thought about IBM Instana Observability is that my concern for the future is only that IBM Instana Observability can add a feature for correlation and recommendations.

The interview was very good and there's nothing I would change for the future. I would rate this review an 8.

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.

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.

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.

I have been using IBM Instana Observability for about two years now.

IBM Instana Observability is stable.

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.

Customer support is good; sometimes it cannot go as deep as I expected, but overall it is good.

I did not previously use a different solution; IBM Instana Observability was the first one that we used.

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.

I think we are some kind of premium partners with this vendor.

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.

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.

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.

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.

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.

I have been using IBM Instana Observability for two years.

IBM Instana Observability is stable.

IBM Instana Observability's scalability is good because the platform uses containers, which makes it scalable.

IBM Instana Observability has ticket support available.

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.

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.

Before choosing IBM Instana Observability, I evaluated other options including DataDog.

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 most valuable feature of the solution is performance. A one-vendor solution serves as a good feature of the tool. In the IT industry, the IT support team has lots of vendors to contact. DB monitoring is done by one company, while WaaS monitoring is done by another and done by another company, which makes it really complicated for the IT team concerned about the security levels. The tool's main feature is that it is a one-vendor solution. The analysis done by the tool is a good feature. The tool is used as an open-source tool. The tool is growing, and new features are being added to the product.

The tool should offer more LDR AI models. The monitoring is just a status, but the next level of a monitoring solution is to prevent an accident or stop an accident status. The solution should be to prevent accidents. Previously, monitoring might have been scanning and alerting and then sending information to the IT manager.

The lack of support is a human resource problem.

I have been using IBM Instana Observability for over three years. My company acts as a partner and reseller of IBM.

It is a very stable solution. Stability-wise, I rate the solution an eight out of ten.

Scalability-wise, I rate the solution an eight out of ten.

My company's clients are medium and enterprise businesses.

I have experience with the solution's technical support. I can't contact IBM's team in the US, but I can get in touch with its team in Korea. IBM in Korea is doing very well, but some organizations are getting smaller, and some people are moving a lot while some organizations are getting bigger. The distributor handled a lot of IBM stuff in Korea. There are three or four distributors in Korea. Actually, we contacted the distributor's technical support team, and then the second one was IBM's Korean support team. Sometimes, we directly ask IBM's sales rep, who handles the technical support teams and our systems. I have been working with IBM in general for over thirty years, but it's not better than what it was in the past.

I rate the support a six out of ten.

Neutral

The product's initial setup phase is not very easy. We can set up a single server. The recommended thing to do is to go for a Kubernetes environment. In a Kubernetes environment, mastering, working, and patching on Odoo can be done after preparing a Kubernetes environment. If I want to make it just a single server, that is fine. One can also use IBM Instana's cloud service.

If ten means a very easy setup process, I rate the product's setup phase as an eight or nine out of ten.

The solution is deployed on the cloud environment.

The solution can be deployed in three to four hours.

I couldn't measure if the tool helped save money, but it may have helped save a minimum of 20 to 30 percent.

The tool's cost is normal as per the market. The tool is not expensive.

The tool is used mainly in the hospitality industry, insurance, banks, and some manufacturing customers.

The biggest value of the product for our customers is that, technically, we embedded some other API solutions, which means some other customers can edit the tool. The tool's customization-friendly nature is good for the customers.

In terms of monitoring and analysis, the tool's hybrid nature is good. The tool can monitor infrastructure, which is available as an optional module. Most of the monitoring solution is to check the service status. After the service status fails, the tool is used to check why it failed. The tool has infrastructure monitoring options with which we can get information about the infrastructure. In general, the tool monitors hybrid infrastructure.

I don't have experience with the tool's AI capabilities. Most people think about AI, but AI must be learned over machine learning. I have to then create LDR, which involves AI modeling. Currently, we do not have a monitoring collection of data modeling, and now it is just the beginning of AI.

In any other industry, the tool is fine. My recommendation about the tool is associated with shopping websites, where there is heavy traffic and heavy applications or services, and for such an industry, it would be very nice to install IBM Instana Observability.

The tool has good performance. The web application's trouble or problems are not exactly because of web application programs, and sometimes, it is because of the infrastructure or database. I can see the one dashboard, so what is happening or what the problem is, can be an area that I can see directly.

I rate the tool a nine out of ten.

IBM Instana is mainly used to monitor microservices on platforms like OpenShift and Kubernetes. It helps in observing the dynamic flow of communication between different layers of the application, such as between the database and the first component.

IBM Instana has enhanced troubleshooting and understanding of application internal communication. It quickly collects data after installing the agent and provides insights into the application's dynamic flow, which aids in identifying issues promptly.

The most valuable features of IBM Instana are its quick data collection and analytics after installing the agent. It swiftly discovers and collects data, providing quick outputs. The dashboards implemented for different entities are also highly beneficial.

One area that requires improvement is related to the automation part, specifically automated actions like sending SMS. This feature needs enhancement.

I have been using IBM Instana for around one to two years.

IBM Instana is quite stable, and on a scale of one to ten, I would rate it eight in terms of stability.

I cannot answer definitively about the scalability of IBM Instana as we have not used it on a large scale. We have mainly used it in small-scale projects.

IBM's technical support is responsive but not entirely satisfactory. The response rate could be better, and as it stands, I would rate the support six out of ten.

Neutral

We use other vendors alongside IBM, such as Microsoft Azure, due to our trust in IBM’s stability and the quick data outputs it delivers.

The initial setup is relatively straightforward, and the installation process usually only takes about one day if all prerequisites are in place.

The implementation is conducted with the client's help and sometimes as part of a team without any third-party assistance.

I'd rate the solution eight out of ten.

The solution is mainly used for observability and application performance management.

The solution has a one-second resolution, giving you the status of your application within one second.

The solution should include log management and improve reporting and integration with Cognos.

I have been using IBM Instana Observability for one year.

IBM Instana Observability is a scalable solution that is usually recommended for enterprise businesses.

The solution’s initial setup is quite easy.

You need to install a single agent to deploy the solution, which hardly takes any time.

The solution's pricing is reasonable compared to that of its competitors like Dynatrace. In India, the solution costs around INR 1,00,000 per node.

IBM Instana's automated root-cause analysis has impacted our incident response times by integrating with other IBM products. A lot of banks are using the tool. Customers immediately see a return on investment with IBM Instana Observability. The solution supports our cloud-native application monitoring strategies. The application can be anywhere because it supports a hybrid cloud.

I would recommend the solution to any enterprise business that is really interested in application performance.

Overall, I rate the solution an eight out of ten.