Dynatrace Reviews

My main use case for Dynatrace is for observability monitoring, specifically to know performance, end-to-end monitoring, and root cause analysis.

From the application side, we need monitoring for the latency, error rate, and request count for the transaction, and also for the digital experience; we want to monitor the analytics of user application. Additionally, for the infrastructure, we want to monitor the utilization of CPU, memory, disk, and network.

For monitoring transactional, it means how many transactions come to our customers in banking.

The best feature Dynatrace offers is APM. When I mention APM, I am referring to Application Behavior Monitoring, and database monitoring is what makes that feature stand out for me.

Database monitoring is very helpful to know the performance of query performance, meaning how much latency there is for the query once called from the application side, and if there is an error from the query, it indicates issues such as ORA errors from Oracle or other errors from PostgreSQL and MySQL or any DBMS.

Dynatrace positively impacts our organization because it is a unified monitoring solution that centralizes the performance of infrastructure, application, and database.

Dynatrace can be improved from the security side because other observability products are enhancing security features, while Dynatrace has room for improvement in this area.

For integration, Dynatrace can improve with WebMethod because it is quite common among our customers using that platform, and they want to monitor their transactions for ESB, which is middleware.

Dynatrace could improve its recommendations, which are not only for cause analysis but also for application performance, infrastructure, and database, including database tuning for the query. I would rate Dynatrace an eight for these reasons.

I have been using Dynatrace for around six to seven years.

Dynatrace is stable.

The scalability of Dynatrace is very significant, especially considering the current improvements in their features, and there is a big opportunity from Indonesia with many use cases for Dynatrace.

The customer support from Dynatrace is very helpful, as they assist our customers effectively when there are problems on the platform side.

I have previously used different solutions such as Datadog and Instana because our customers are selling three products of observability.

For the investment, Dynatrace is very helpful for our customers because they can see the transactions through Dynatrace and save money by identifying problems, thereby reducing monetary losses on their application side.

For pricing, we use the Classic model, specifically DPS, which stands for platform subscription. The cost can be controlled from our side, and it is very transparent with Dynatrace regarding DPS and licensing.

The first time we used Dynatrace, we did not evaluate other options, but later considered Datadog, Instana, and Elastic APM.

My advice for others looking into using Dynatrace is that recommendations are very helpful for our customers, as many products provide numerous recommendations. However, Dynatrace focuses mainly on monitoring operations and providing root cause analysis without offering much in the way of recommendations, which I believe is important for observability products.

Our company has a business relationship with Dynatrace beyond being just a customer; we are both a partner for local support and a reseller for licensing. I rate this product an eight out of ten.

Dynatrace encompasses several areas for our organization, including incident management and release management. We also use it for marketing purposes to reduce MTTD and MTTR. We use it for user journey mapping so we can understand how our customers are experiencing our portals. We have a driver to never have a customer tell us when we have an issue again, and we have achieved that by using Dynatrace with targeted alerting and a robust service management process to support it.

Our use cases focus on reducing customer outages, anticipating customer issues, fixing them before they become problems, supporting digital marketing purposes, managing incidents, and managing releases, alongside fixing some legacy issues encountered once we implemented Dynatrace. Lifting the lid on applications helped us see where we were losing business, leading to a positive return on investment. Currently, our main use case is for integration, release, incidents, and more on digital journeys.

A specific example of how Dynatrace has helped in one of those areas involves using BizEvents to map key pages and transactions within our portals, which helps us understand how long it takes for a customer to get a quote, update a quote, or do a mid-term adjustment. We can also look at the quote to buy conversion ratio...

Dynatrace has positively impacted our organization with metrics reflecting a 60% reduction in MTTD, and we continue to reduce our MTTR, aiming to bring it down another 30 or 40%. By addressing some legacy issues early on, determined to hold a quote value of around a million pounds a year, we have seen significant customer experience improvement regarding the quote journey...

The best features that Dynatrace offers, in my opinion, include distributed traces, integration with ServiceNow and Jira for automatic ticket logging, and real user monitoring, which provides significant understanding of how our customers feel when using our systems. I also find logs extremely useful for troubleshooting; logs provide brilliant information...

Improvement suggestions for Dynatrace are challenging, given its complexity and capabilities. However, I do find that some documentation can be quite tricky to read. I believe that enhancing the documentation and providing how-to videos would be beneficial...

I have been using Dynatrace for two and a half years.

I present a nine rating for Dynatrace due to several factors; primarily, the functionality within the portal is outstanding. Dynatrace support, particularly with the ESS agreement, is incredible...

In our organization, we deploy Dynatrace as a SaaS solution, complemented by an ActiveGate server on our private cloud.

We measure the reduction in MTTR and the impact on revenue by analyzing our ServiceNow statistics. We observe the time a ticket is opened and when it is closed...

We acquired Dynatrace through SCC. Our environment comprises two clouds: AWS and Azure.

My advice for others considering Dynatrace is to embrace the enterprise support agreement and engage with your consultants early on, as you will realize value quickly...

Hybrid Cloud

Other

I use Dynatrace in my project to monitor EC2 instances and ECS containers and track application performance, detect infrastructure, service, and container issues. In my project, I use Dynatrace for full-stack monitoring.

The best features Dynatrace offers include configuring alerts and dashboards, such as problem notifications and custom dashboards for EC2 health, ECS service performance, error rates, and latency, along with anomaly detection and security and IAM, allowing outbound traffic to Dynatrace and using IAM roles for EC2 with no sensitive data stored locally. In my project, I use Dynatrace OneAgent on EC2 and ECS to monitor the infrastructure, containers, and application performance, providing automatic service discovery, real-time metrics, distributed tracing, and AI-based root cause analysis.

Dynatrace can be improved by fine-tuning AI-based settings.

I feel that improvements around API rates and latency could be beneficial.

I have been working in my current field for the past three to four years.

Dynatrace is stable in my experience.

The scalability of Dynatrace is good.

Customer support is excellent; whenever I raise a ticket with the vendor, they immediately connect with me and help me.

Positive

Previously, I used only CloudWatch, but I switched to Dynatrace because the features in Dynatrace are not found in AWS CloudWatch.

Dynatrace is deployed in my organization in the AWS cloud.

I did not purchase Dynatrace from the AWS Marketplace; I hosted Dynatrace on AWS.

I have seen a return on investment in terms of time saved.

My experience with pricing is that it costs $58 per month for full-stack monitoring.

I did not evaluate other options before choosing Dynatrace, as I only selected Dynatrace.

I advise anyone looking to set up a monitoring system in their project to consider Dynatrace because it will monitor their infrastructure, servers, and application performance, providing automatic service discovery and real-time metrics; it is the best option to choose or set up in their project. I gave this review a rating of 9 out of 10.

Public Cloud

Amazon Web Services (AWS)

There are three major things that I look for. The first is that it is undoubtedly tier one, as per Gartner. This lowers the risk of product performance. Dynatrace has a good presence from an APM perspective, application performance perspective, where it can be easily configured. 

There are many adapters and solutions available in the market. In every organization, like ours, there are a few more built-in adapters. 

From an enterprise perspective, due to the higher cost, higher stability, and several considerations for high-level architecture, I take care of security perspectives, providing a stable solution. 

For system integrators, it is good from an operational perspective since there are many SLAs, so larger organizations generally opt for tier one solutions where they can have fewer operational issues, avoiding SLA penalties.

Graduation features offered by Dynatrace provide a single view and can connect with many other monitoring systems. Importantly, it delivers real-time insights. 

Additionally, Dynatrace positively impacts my organization in various ways.

There may be an issue since there are many tools like Splunk involved in network monitoring. From an IP perspective, Dynatrace is performing well. If they want to develop in network monitoring, they can, as it's part of their product line. It's not rocketry, so they can accomplish it. If I, as an SI, look at it from an enterprise perspective, considering the cost from the client, I prefer not to go with multiple systems, as they don't provide a complete 360-degree view. They need to improve on claims about being an enterprise system. The definition of enterprise is loosely used, however, from a holistic security perspective, including infrastructure, network, ports, software, applications, transactions, and databases, there are areas lacking, especially in network monitoring tools.

I have used the solution for the last four years, just for four years only.

Stability depends on the deployment, the person deploying it, and how the configuration is done. Generally, all are stable at ninety-nine point nine nine percent, but if the underlying infrastructure is not deployed correctly, stability may be problematic. This is a very relative term, and no software can exist alone at ninety-nine point nine percent. If the infrastructure doesn't support it, it cannot exist as standalone. Deployment location, whether in triple nine data centers, double nine data centers, or other types, also matters. If power is lost, stability is affected, depending on how it's deployed.

Scalability is easy. All opportunities work on the agent number and server transactions that need monitoring. If you include those things, some are agent-based, and some are agentless. The monitoring is done based on licenses, like tier or enterprise licenses. It depends on what the client is looking for. If it's an enterprise, increasing the number of instances doesn’t pose problems.

Their support system is good. I would rate them at 9.5 out of ten. People generally don't pursue it since it's a monitoring system itself. They have a good reputation, and the support is commendable. People are helpful, even with delivery and other related aspects. I use their excellent support system.

Anand, this is reflective work. These setups are complex, meaning significant thought is required. It's a relative aspect, however, developers could have clearer insights. Today, products in the market are packaged, just requiring configuration. Collecting logs, tagging events, and other aspects are relatively straightforward and not considered complex.

Determining ROI is subjective. Monitoring is passive, merely aiding business processes and not active within them. ROI is hard to specify; however, incidents like impending ransomware attacks highlight its value, though those are exceptional events. Return on investment in predictive analytics and AI tools is minimal, given the passive nature of these systems.

Clients sometimes opt for alternatives based on budget constraints. If the budget is small, tier two solutions like Elasticsearch may be considered. It varies by location, like in Singapore, where tier two solutions are viable options.

I give the solution nine out of ten. Enterprises typically choose Dynatrace, especially when the IT system budget is around a $100 to $200 million. Investing an additional $120 million makes sense. If your system is worth $50 million, the investment doesn’t exceed 1.2%. ROI considerations are tied to observability, dependent on how the business values these aspects.

My main use cases with Dynatrace include a plethora of functionalities. Real user monitoring (RUM) is being used extensively. Synthetic monitoring is used extensively. We use Kafka monitoring. I have awareness of how AWS metrics are being sent, whether it's a direct integration or only account-level integration. We use it significantly.

Some of the best features I appreciate about Dynatrace include synthetic monitoring, where you can get into HTTP level monitoring and click browser monitoring, which is available in both Splunk and Dynatrace. This is very useful in our environment. Apart from that, mobile-based monitoring, which we have embedded in some cases with the apps that are connected, is also beneficial for monitoring APIs.

Synthetic monitoring has had a significant impact on my ability to track performance proactively. It has been very useful. It serves two aspects: synthetic monitoring is primarily for the front-end side where availability and tracking whether the website is running, and we can verify if users are able to log in and see things running.

From the infrastructure point of view, the availability of the infrastructure at AWS level with Kafka, EC2 instances, and Lambda functions is covered for the monitoring system and infrastructure team. We are catering to both audiences.

Dynatrace's AI-driven Davis engine absolutely helps identify performance issues by showing root cause analysis for us up to 200%; whatever is integrated, if it is visible, it can stitch and show.

The comprehensive application topology visualization in Dynatrace, called Smartscape, has benefited my understanding of system dependencies. Even though Splunk has something similar, since we are using Dynatrace primarily for observability, we can get top-to-bottom visibility, from infrastructure to network to application front end. When integrated based on application requirements, we get a good grasp of what's happening during issues.

Dynatrace could be improved primarily with regards to pricing. These tools are expensive. They have been the pioneers from inception, and they remain at the top of the Gartner chart. The quicker we learn, the better we can serve is what the team believes.

Learning is another aspect that needs improvement, specifically how the tools can educate users. Education needs to be tailored differently for front-end user monitoring, infrastructure-based monitoring, and centralized monitoring teams. The segregation of educating how to use the tool is something we have recommended to all tools teams and product owners.

They could help with more learning capabilities. A monitoring tool will be used by different types of users. One is from the infrastructure point of view. Another is an application developer who wants to see if strings are getting attached and code-based applications are being stitched together. A front-end monitoring person or business wants to know about website and infrastructure availability, and what kinds of dashboards they can create for their comfort. That's how a tool gains visibility and inclusiveness. It depends on the owner of the tool to address these different aspects and let users choose their preferred way to use the tool.

I have nearly six years of experience with Dynatrace.

Regarding the initial setup, while I can't speak for how my company implemented it overall, I can say that the Dynatrace setup is good enough, not an issue. Integration with the cloud is straightforward. In cases of new aspects of cloud, some drilling is needed to determine installation possibilities. That's a challenge in the cloud - whether to integrate with the cloud directly or opt for agent installation. These issues arise when new features or services are enabled in AWS; parallelly, Dynatrace and Splunk and these tools need to adapt to see if these services can be monitored. Users start asking if we can enable new AWS features in our tools. This synchronization should happen at the back end; users should not be involved in that process.

I think Dynatrace's customer service and technical support for this product is good. Out of five, it rates nearly four. This is good enough to expect.

Positive

The monitoring team is able to work without any user intervention, which is appreciable. Comparing to other tools such as Splunk, CloudWatch, or other tools which I have researched for RFPs, I feel DataDog is good enough. However, based on the experience from my users, Dynatrace is more flexible for them.

We deal with APM solutions and monitoring or logging solutions by having Splunk already in place in my environment, along with Dynatrace. We have other tools such as CloudWatch.

I have dealt with Splunk on-call and have all kinds of experience. I have used the PeerSpot platform extensively, and it does help significantly. I will be happy to provide individual product reviews.

On a scale of 1-10, I rate Dynatrace an 8 out of 10.

Amazon Web Services (AWS)

Amazon Web Services (AWS)

My main use case for Dynatrace is observability of production workloads. A quick specific example of how I use Dynatrace for observability in my production workloads is to monitor and observe the performance in context of various applications that our company runs.

Dynatrace has positively impacted our organization because we had various tooling before, with different teams using different tools, leading to our observability and monitoring being dispersed across several tools. We consolidated that down into a single tool being Dynatrace, bringing everybody into one platform and one pane of glass.

This consolidation to one platform has affected my team's efficiency and collaboration by showing the biggest improvement in cross-team collaboration and visibility. The NOC is able to see across the various products and services during live issues without having to jump into different tools to see the context; it is all there on that single pane of glass, which greatly improves efficiency and reduces our mean time to resolve.

The best features Dynatrace offers are the ease of administration and configuration, the single pane of glass, the contextual view of logs, metrics, and traces, and overall, it is a well-balanced product.

The single pane of glass and contextual views have helped me and my team day-to-day by making things easier when we are troubleshooting issues in production because we get the context of one application versus the other applications in the environment, which is easier for pinpointing root cause analysis. Having the various metrics, logs, and traces all in a single pane of glass provides comprehensive visibility.

For me, the main area for improving Dynatrace is in the architectural overview map that they provide; it would be beneficial if it were simpler to use because it is currently a little cumbersome.

The tool that I refer to when discussing needed improvements is called Smartscape. I find that it is a little overwhelming and cluttered when I access it, so simplifying that Smartscape tool would be of great advantage.

I have been using Dynatrace for two years.

Regarding Dynatrace's AI capabilities, we do not use the governance and security model at this stage. Regarding Dynatrace's AI capabilities, its accuracy and reliability of output seem solid.

Dynatrace is deployed in our organization using public cloud, on-premises, and we utilize the SaaS offering from Dynatrace. We use GCP, AWS, and Azure as our cloud providers. I do not think we purchased Dynatrace through the AWS marketplace.

The advice I would give to others looking into using Dynatrace is that it offers the ability to have more than one tenant, so I would always recommend setting up a sandbox environment alongside the production environment and possibly even a non-production environment, just to split up the various environments and provide the technical teams with a sandbox in which they can confidently configure and change things without impacting production. I would rate Dynatrace a nine out of ten.

We decided to integrate Dynatrace primarily to monitor the availability and latency of our applications. We have a significant number of applications, and we needed a system that could manage their availability. Previously, we lacked evidence to show whether an application was available when a customer raised an issue. With Dynatrace, we can verify this information, even after a month.

Dynatrace offers exceptional features compared to other monitoring tools. It allows the creation of different dashboards related to application availability and server latency. The integration with Power BI for generating detailed reports is a standout feature. Furthermore, the automation of alert management, which integrates with ticketing systems to automatically raise and assign tickets, is a significant advantage over tools like Centreon. Dynatrace also integrates with AI tools to generate business reports.

When making comparisons with other tools, Dynatrace stands out, but it is a bit complex to understand and implement on servers. There are occasional issues with language and text, which can be frustrating. Despite this, it remains superior to Centreon.

I started using Dynatrace six months ago.

There have been no stability issues with Dynatrace. It is well-maintained and, being supported by cloud infrastructure, we have experienced no interruptions.

We have faced no scalability or reliability issues with Dynatrace. Everything functions smoothly.

The technical support from Dynatrace is excellent. Recently, we had an issue, and the support team resolved it within 20 to 25 minutes. Their support is very fast and effective.

Positive

In the past, I used Icinga and Centreon. Compared to these, Dynatrace remains the top priority. Its features surpass the typical expectations for monitoring tools.

The implementation of Dynatrace was handled by a different team, so I don't have insights into their process.

The integration of Dynatrace has allowed us to monitor application stability and create business reports. However, I haven't quantified the ROI.

Dynatrace is known to be costly, which delayed its integration into our system. However, the advanced features it provides are unmatched, making it a valuable investment for organizations with a higher budget.

I highly recommend Dynatrace for organizations with a significant budget because it decreases resource costs and manpower. It is a versatile tool for IT organizations, providing features that are beneficial for comprehensive application monitoring. I rate Dynatrace a 9 out of 10.

Public Cloud

Amazon Web Services (AWS)

Whenever we do any kind of performance or load testing with Dynatrace, we monitor the environment using service dashboards, deep distribution tracing, analyzing response time hotspots, method hotspots, and understanding the service flow while correlating all this with our load testing results and sharing the feedback with the stakeholders.

We don't use anything related to CI/CD on Dynatrace, but we use it through LoadRunner Enterprise.

I find the classic service analysis, service analysis, distribution tracing, and the technology stack that it shows most valuable about Dynatrace, along with the Scape View. I'm unable to pronounce the exact name, but there is a Scaped View, Scaled View, or Scape View where I can see all the environments and how they are configured.

We use AI-powered anomaly detection from Dynatrace, specifically Davis AI log analysis.

The effectiveness of Dynatrace's user experience monitoring is very useful.

I'm using Dynatrace for full-stack monitoring.

I think Dynatrace almost looks good, but I believe we should improve how we can integrate with AI. I'm specifically looking at AIOps and how we can monitor AIOps-related things, considering we have LLMs and all that stuff. I don't see those monitoring capabilities for NVIDIA chips, NPUs, GPUs, or anything similar, and maybe it has them, but unfortunately, I lack the knowledge to understand where I can view all those things.

I've been working with Dynatrace for nearly five years.

I would rate the stability of Dynatrace approximately between nine and ten.

The ability to scale and expand in Dynatrace rates around nine to ten altogether.

For Dynatrace tech support, we have a dedicated team here, which is easily reachable, so I rate it around nine to ten.

Positive

I'm not using AppDynamics currently. We used to use it, but now we are using Dynatrace. I moved to Dynatrace completely from AppDynamics.

Dynatrace is basically set up by a Dynatrace admin. OneAgent is installed on one machine, and the entire thing gets monitored through Dynatrace.

JMeter and BlazeMeter are the other vendors I'm working with. I'm only using JMeter from Apache, not using Tomcat or something similar.

The main benefit of Dynatrace is that it's easy to understand where exactly the issue is. When you see the PurePath, you know which particular machine or hop the application is having an issue with, allowing us to easily drill down to what is happening with the application. If something is happening on the UI, you want to understand what's wrong with the request, and to do that, you need to analyze Dynatrace to easily understand the root cause and where exactly you're seeing the issue.

The Dynatrace license is at the client's location; the client has purchased it, and we just use it.

Without any doubt, Dynatrace is preferable compared to AppDynamics. The main reason why Dynatrace is better is that you can see everything in one go; it includes log analysis, AWS analysis, component level analysis, PurePaths, distribution tracing, real user metrics, mobile metrics, all in one particular tool, one solution.

On a scale of 1-10, I rate Dynatrace a 10.

On-premises

Amazon Web Services (AWS)

Our primary use case for Dynatrace is full-stack monitoring. We use it to monitor the performance and availability of our applications, infrastructure, and services. It helps us quickly detect issues, analyze user behavior, and perform root cause analysis using AI-powered insights.

Dynatrace has significantly improved our organization by providing full-stack visibility and automated root cause analysis. It helps us detect and resolve issues faster, reduce downtime, and improve user experience. The OneAgent simplifies deployment, and the AI-powered insights allow our team to focus on innovation instead of firefighting.

We use Dynatrace full-stack monitoring because it allows us to trace issues across the entire stack — from user interactions to backend infrastructure. It’s very effective for identifying where problems occur, making it highly valuable for end-to-end observability.

Dynatrace's user behavior monitoring and analysis also works well. It provides powerful insights into user interaction patterns, session behavior, and user experience metrics, which help us understand how our applications are being used.

One of the features I appreciate most is the OneAgent. We only need to install a single agent per host, and it automatically collects metrics, logs, traces, events, and more — without requiring multiple separate tools or manual instrumentation.

We also benefit from Dynatrace’s AI-powered anomaly detection. The Davis AI engine detects unusual patterns, performs root cause analysis, and sends smart alerts — all automatically, which significantly improves our incident response time.

More customizable dashboards

Better log search and retention features

Easier tagging and permission management at scale

Improved mobile app monitoring support

reduction in costpricing 

I have been working with Dynatrace monitoring and other monitoring systems for about three years. During this time, I’ve gained hands-on experience with full-stack observability, user behavior analysis, anomaly detection, and automated root cause analysis using Dynatrace.

Dynatrace is very stable and reliable. Its OneAgent runs with minimal impact on system performance, and the platform itself experiences very few outages. Regular updates and proactive monitoring by Dynatrace ensure high availability and consistent performance, which is critical for our continuous monitoring needs.

Dynatrace scales very well across different environments, from small setups to large enterprise systems. Its automatic discovery and instrumentation make it easy to manage thousands of hosts, containers, and services without significant overhead. The platform handles high data volumes efficiently and maintains performance, making it suitable for dynamic cloud-native and hybrid environments.

My experience with Dynatrace customer service and support has been positive. The support team is responsive and knowledgeable, providing timely assistance for technical issues. Additionally, the available documentation and community resources help resolve many questions quickly. Occasionally, complex issues may require escalation, but overall, the support experience is reliable.

Neutral

We previously used a full monitoring system with Zabbix, which worked well but required a lot of manual configuration and maintenance. With Dynatrace, we benefit from extensive automation tools that significantly reduce manual effort. This automation is a key difference that sets Dynatrace apart from Zabbix and other monitoring solutions.

The initial setup of Dynatrace is generally straightforward thanks to the OneAgent, which automates discovery and instrumentation across the environment. However, configuring advanced features, custom dashboards, and integrations can be more complex and may require some learning and planning. Overall, the automation significantly reduces manual effort compared to traditional monitoring tools.

Dynatrace is ideal for clients who need advanced, automated monitoring. However, some clients may not fully understand its value and might not need to invest in a high-end solution if their requirements can be met with free tools like Zabbix.

The SaaS version of Dynatrace is typically suitable only for proof of concept (POC) purposes. When customers commit to Dynatrace, they usually opt for the managed version for production use.

Overall, I would rate Dynatrace 9 out of 10 as a product solution.

On-premises

Microsoft Azure

Our primary use case for this solution is infrastructure and application monitoring. A total of 90% of our applications are on-premises and we are moving to the cloud, and this solution is helping us monitor that transition.

This solution has helped our organization on multiple occasions. The synthetic monitor came in particularly handy. We also deploy the solution to monitor hundreds of our customer-facing sites for any outages, etc.

The feature I found most valuable when it comes to this solution is the AI engine. It can correlate and collate different types of alerts and show us the most probable root cause.

I would say that this solution's reports are lacking a little bit, and because of this, you have to rely on API to fetch and pull data. I think they could have done a bit of a better job by providing a more user-friendly search from a reporting perspective.

I have been using this solution for about five years.

I would rate the stability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

I would rate the technical support of this solution a 10, on a scale from one to 10, with one being the worst and 10 being the best. The reason for this rating is that we pay for premium support with them.

Positive

I would say that five years ago when we did the initial setup, we had some issues. However, I think that this process has changed since then.

I would say that we have seen a return on investment.

We are typically about a version or two behind. We are on the managed solution.

Our model of deployment is on-premises. I would say there are a couple of thousand users of this solution in our company. We are also planning on increasing the usage as our apps migrate to the cloud.

I would advise other people looking into solutions, to do their homework beforehand and not assume that by deploying all the tools everything will automatically work, so there's still a lot of configuration involved.

I would rate this solution as a whole an eight, on a scale from one to 10, with one being the worst and 10 being the best.

On-premises