Dynatrace Reviews

Our company uses the solution to identify performance issues. Our database is in Oracle and our user interface is Maps. The solution helps us to gather required information and manage systems. 

For example, we just had a big data center issue with cluster settings, voting, and updating. The solution captured the issue and showed us that shutting down the data center would not solve the problem because data was not flowing from the DR side. This is one of the best use cases because the solution captured the issue so well that we didn't need help from another application or database team. We were able to identify the issue, correlate it, and provide information immediately. 

It is very easy to create customized dashboards.

The solution is more user friendly than other application performance products.

Issues are identified more accurately than with other products. 

Though I have never used it, I hear that the container platform could include more value-added features. 

I have been using the solution for one year. 

The solution is stable, includes good vendor support, and provides frequent updates. 

The solution is easy to scale through the active gate. 

We have more than 100 users across our infrastructure or enterprise applications and plan to increase usage in the future.

I have only interacted with support a few times but the team works closely with them and gives good feedback. 

I rate technical support an eight out of ten. 

Positive

We are currently migrating from AppDynamics to the solution. 

AppDynamics is moving toward a fast model and has a few issues with vendor support. It also requires multiple agents for each function. For example, a Java-related APM requires the installation of another agent. 

The solution is a bit higher priced than AppDynamics but is more user friendly and only requires one agent, so our application teams prefer it. 

The setup is very straightforward and it is easy to onboard. 

I rate setup an eight out of ten. 

We use Great Logics provisioning tool to install the solution's agent, package it, and distribute it to end users. Installing and provisioning takes about five minutes. 

There is no maintenance because upgrades happen from the centralized server. The process is much simpler than other products because many of them require another agent for upgrades.  

The pricing is a bit on the higher end and more expensive than AppDynamics. 

When we compared the solution with other APM tools, we found that its features and uniqueness balance out the price well. 

Pricing is rated a six out of ten. 

I recommend the solution, specifically if you want to find your root causes before issues become bottlenecks. 

The solution is a really good product and I rate it an eight out of ten. 

It tells me everything I need to know. It tells me what the transactions are. The AI provides you with advancements or degradations in what is happening. 

It gives me visibility into everything, from transactional logs to services and processes to the OneAgent installed on the box, which tells me it's talking to systems that are in development and it shouldn't be.

The most important takeaway is simply the compute. Simply understanding how much, or, the resource adoption across the board. Back in the day, for example, I would need 128 gigs of RAM to run SQL. You don't need that any longer. Having the performance and true metrics of what's going on, as well as scaling your environment to its optimal performance.

Dynatrace works perfectly.

Having OneAgent is the most valuable feature of Dyantrace, as well as the monitoring.

What is web interaction as it relates to Synergy, or when it comes to using web-based, phone-based, or apps published on end-user devices, it's fantastic in terms of performance, and code. Even if you run the release and discover that the update you just released is causing a degradation in performance, auto-release will restore the old code without missing a beat.

I believe that something related to IoT devices should be improved.

I have been using Dynatrace since 2018. It's been four and a half years.

We are using both a SaaS and an on-premises version.

It is both on-premises and hybrid.

They are hosted by Google, Microsoft Azure, as well as AWS.

Dynatrace is a stable solution. It's rock solid. We have never had an issue.

Dynatrace is scalable. I would rate it a nine out of ten.

We have an application, management, and support teams looking into things. We have our help desk and service desk looking at various dashboards. Certain dashboards are being examined by our developers. It is frequently used by between 60 and 80 people.

I believe we are currently using all of the functions and features. It's operational, it's production, it's living and breathing.

I would rate the technical support a four out of five.

Positive

We were looking at Dynatrace at the time, and then there was AppDynamics or something like that, I believe, which Cisco eventually purchased. Dynatrace's maturity level at the time far outstripped that of anything else on the market.

In 2018 it was a superior product.

The initial setup is straightforward. I'll be up and monitoring in four hours. The on-premises installation was a little more difficult due to network firewalls and so on. Overall, it went well.

This solution can be deployed and maintained by four people.

For us, the most important thing was to get OneAgent out everywhere. Once we had the OneAgent in place, we began building out, and understanding what applications are present, and start developing the monitoring aspects. Not just from conventional RAM CPU calculations, but truly looking at the applications, and examining the Java functions, as well as the MongoDB functions.

Having all of that information and being able to create dashboards to communicate it not only to the higher-ups but also to the developers doing the development, who must understand that they must be very smart with their code.

We are a consulting company. Within our organization, we have a Dynatrace division. However, for this installation, in particular, we collaborated with Dynatrace on product implementation.

We saw a return on investment. The downtime has been reduced, which is significant in and of itself.

I would rate the return on investment a five out of five.

I am not aware of the licensing fees.

We evaluated AppDynamics.

I would recommend following the instructions. It's easy to understand.

Nothing is very perfect. I would rate Dynatrace a nine out of ten.

We are using it to monitor our e-commerce applications and the full stack that our e-commerce applications run on. That includes both our Rack Room Shoes domain and our Off Broadway Shoes domain. We use it to monitor the overall health of the entire stack, from the hardware all the way to the user interface. And more specifically, we use it to monitor the real user's experience on the front-end.

What Dynatrace has really allowed our team to do is focus more on innovation, rather than on monitoring and bug-squashing. Now that we have a tool like Dynatrace, we can continue to do forward-thinking projects while Dynatrace is doing the monitoring and rooting out the root causes. We're spending a lot less time trying to find out what the problem is, versus letting Dynatrace pinpoint where the problem is. We can then validate and remediate much quicker. That's the impact it's had on our business.

The automated discovery and analysis helps us to proactively troubleshoot production and pinpoint underlying root cause. We recently had some issues with database connections. Our database team was scratching their heads, not really knowing where to look. What we were able to do with Dynatrace, because we had some of the Oracle Insights tools built into the database, was to provide, down to the SQL statement, what queries were taking up the most resources on that machine. We provided that to the database team and that gave them a head-start in being able to refactor the data so it was quicker to query. That really helped us speed up the user experience for that specific issue.

Dynatrace helps DevOps to focus on continuous delivery and to shift quality issues to pre-production. We are just now starting to use it in that way. When we first launched Dynatrace, we only had monitoring in our production environment. At that point we were using it as an up-front, first-alert tool for any issues that were happening. Now what we're doing is instrumenting our lower environments with Dynatrace so that it will allow us to monitor our load-testing in those environments, to find out where our breaking points are. So it does allow us to push out products that are much more stable and much less buggy because we're able to find out where our breaking points are in the lower environments. What this is going to do is allow us to do is push out, at a faster rate, more solid, less buggy releases and customer features, and allow us to continue to innovate on the next idea. We're just starting that journey. We just got fully instrumented in our lower environments in the last couple of weeks.

In terms of 360-degree visibility into the user experience across channels, we're only monitoring our digital channels right now, specifically our e-commerce channels. But we do have ways, even within the channel, to dissect by the source they came from. Did a given customer come from a digital ad? Did they come from an email? Did they come to us direct? It does allow us to segment our customers and see how each segment of customer performs as well. This is important for us because we want to make sure that we're not driving specific segments of customers into a bad-performing experience or to a slow response time. It also allows us to adequately determine where to spend our marketing dollars.

Another benefit is that it has definitely decreased our mean time to identification, with the solution and the Davis AI engine bringing the most probable root cause to the top. And within that, it gives us the ability to drill down into the specific issue or query or line of code that is the issue. So it has saved us a lot of time — I would estimate it has saved us 10 hours a week — in remediating issues and trying to find the root cause.

It has also improved uptime, indirectly. Because it gives us alerts early, we're able to mitigate issues before they're actually bigger issues.

The alerting systems are definitely the most valuable feature. The AI engine, "Davis," has proved to be a game-changer for us, as it helps to alert us when there are anomalies found in our applications or in their performance. We find that very helpful. There's still a human element to the self-healing capabilities. I wish I could say, "Oh, it's magic. You just plug it in and it fixes all your problems." I wouldn't say that, but what I would say is that the Davis engine gives us that immediate insight and allows us to cater to our solution so that the next time that problem arises it can mitigate it without a lot of human involvement.

Dynatrace's ability to assess the severity of anomalies, based on the actual impact to users and business KPIs, is really good, out-of-the-box. But it does an even better job when, again, we as humans give more instruction and provide more custom metrics that we're trying to monitor that are key to our business. And then, letting the Davis engine find those anomalies and push them to the top, especially as they relate to business impact, is very valuable to us.

We find the solution's ability to provide the root cause of our major issues, down to the line of code that might be problematic, to be valuable.

And we get a lot of value out of the Session Replay feature that allows us to capture up to 100 percent of our customers' real user experiences. That's helped us a lot in being able to find obscure bugs or make fixes to our applications. 

We also use real-user monitoring and Synthetic Monitoring functionalities. We use real-user monitoring for load times, speed index, and overall application index. And we use Synthetic Monitors to make sure that even certain outside, third-party services are available to us at all times. In certain cases, we have been reliant on a third-party service, and our Dynatrace tool has let us know that that service isn't available. We were able to remove that service from our website and reach out to the service provider to find out why it wasn't available.

We also find it to be very easy to use, even for some of our business users. Most of the folks who use the Dynatrace tool do tend to be in the technical field, but use is spread across both the business side, what we call our omni-channel group, as well as our IT group. They all use it for different purposes. I'm beginning to use it on the business side to show the impact that performance has on revenue risk. I can then go back and show that when we have bad performance it affects revenue. And I can put a dollar amount on that. So the user interface is very easy to use, even for the business user.

Dynatrace continues to innovate, and that's especially true in the last couple of years. We have continued to provide our feedback, but the one area that we get value out of now, where we would love to see additional features, is the Session Replay. The ability to see how one individual uses a particular feature is great. But what we'd really like to be able to see is how a large group of people uses a particular feature. I believe Dynatrace has some things on its roadmap to add to Session Replay that would allow us those kinds of insights as well.

We started using Dynatrace in September of 2017. At that time it was an older product called AppMon. But we quickly upgraded to the current Dynatrace platform the following year. We've been using the SaaS platform ever since.

It's been very stable. We've had very little downtime. In the last four years there may have been one outage. Overall, it's been extremely stable. Many times, Dynatrace is our first alert that we have issues with other platforms.

It's extremely scalable. We're one of the small players. We're running with about 70 agents right now. We've been at Dynatrace's conferences and have heard of customers who can deploy 5,000 agents over a weekend and have no issues at all. For our small spec-of-sand space, it's extremely scalable.

We are hosted on Google cloud. That's where all of our VMs are currently set up. Our database is there, our tax server is there. All of our application and web servers are there, and Dynatrace is monitoring all of that for us. We haven't encountered any limitations at all in scaling to our cloud-native environment. We can spin up new auxiliary servers in a matter of minutes and have Dynatrace agents running on them within 15 minutes. We're starting to play a little bit with migrating a version of our application into a Kubernetes deployment and using Dynatrace to monitor the Kubernetes containers as well.

We have plans to increase our usage of Dynatrace. We just recently updated our hosts. We needed to increase the number of host units so that we could put Dynatrace on more servers, and we've already just about used up all of those. So next year, we'll likely have to increase those host units again. And we're going to start using more pieces of Dynatrace that we haven't used before, like management zones and custom metrics.

Technical support has been great. The first line of defense is their chat through the UI, which is really simple. They're super-responsive and usually get back to us within minutes. We have a solutions engineer that we can reach out to as well, and they have been very helpful, even with things like setting up training sessions and screen-sharing sessions to help enable our internal teams to be more productive using the tool.

We were using a tool called New Relic and we were really just using it as a synthetic monitor to make sure the application was up and running, but we really weren't getting a lot of insights. When we decided that we wanted a tool that could give us more insights and that we needed a tool that could give us the ability to monitor more of our customers' behaviors, there just wasn't another tool like Dynatrace that we felt could do things as well as Dynatrace, through a "single pane of glass." We chose Dynatrace over New Relic at the time because New Relic just didn't have any solutions like it.

We haven't found another tool that can help us visualize and understand our infrastructure, and do triage, like Dynatrace. We haven't found one that can give us that full visibility into the entire stack from VM all the way to the UI. That was really the reason we picked Dynatrace. There just wasn't another tool that we felt could do it like Dynatrace.

The fact that the solution uses a single agent for automated deployment and discovery was the second reason that we chose Dynatrace. The ease of deployment, the fact that we could use the one agent and deploy it on the host and suddenly light up all of these metrics, and suddenly light up all of these dashboards with insights that we didn't have before, made it extremely attractive. It required a lot less on our part to try to do instrumentation. Now, as we add more Dynatrace agents to more of our back-end servers, we think we'll gain even more value out of it.

We started with AppMon, which was more of an on-premise version, where we were installing it, although it still was a one-agent. Then we moved to the SaaS solution, and it was very easy for us to migrate from AppMon to the SaaS solution, and it's been extremely easy to instrument new hosts with the agent.

We were up and running within 30 days when we were first engaged with AppMon. When we migrated to the SaaS solution, it maybe took another 30 days and might have even been less. I wasn't involved with that migration, but I worked closely with the guy who was. I don't remember it taking much longer than 30 days to migrate.

We had an implementation strategy. We knew specifically which application we wanted to monitor, and all of the hardware and services and APIs that that application was dependent on. We went in with a strategy to make sure that all of those things were monitored. And now we've progressed that strategy to start monitoring more of our internal back-end systems as well — the systems that support our stores, not just our e-commerce channel — to see if we can't get more value and maybe even realize more cost savings on our brick and mortar side using Dynatrace.

We have definitely seen return on our investment. It has come in the form of being able to produce more stable, less buggy applications and features, and in allowing our team to focus more on innovating new ideas that drive revenue and business, versus maintaining and troubleshooting the existing application.

It hasn't yet saved us money through consolidation of tools, but as we continue to find more value in Dynatrace, it does make us look at other tools and see if we are able to use Dynatrace to consolidate them. We have replaced other application monitoring tools with Dynatrace, but we've not yet consolidated tools.

Whatever your budget is, you can manage Dynatrace and get value out of it, but you need to manage it to what your needs are. That's the one thing we found. We did not budget the right amount to begin with. It has cost us more in the long run than if we would have been able to negotiate it upfront. But we didn't really know what we didn't know until we'd been using Dynatrace for awhile.

Your ability to catch your Session Replay is based on the number of what they call DEM units, digital experience monitoring units. That's where we were short to begin with. There is an additional expense to determining not just the platform subscription but also the number of hosts units that you want to run and the number of DEM units that you need to be able to capture all of the user experiences that you want. In our case, we wanted the ability to capture 100 percent. Maybe in another business someone would only be worried about capturing a sampling of the traffic.

We evaluated New Relic, AppDynamics, AppMon, which was the Dynatrace solution at the time, and we also looked at Rigor.

Dynatrace could do pretty much everything. It wasn't just the real-user monitoring piece of it. It was also the full stack health aspect. The Davis AI engine was probably the biggest differentiator among all of the tools. The Davis AI engine and its ability to surface the root cause was a game-changer.

My advice would be to jump all-in. There doesn't seem to be another tool that can do it like Dynatrace, and from what we've seen the last two times we've gone to their Dynatrace Perform conferences, they are dedicated to innovating and adding features to the platform.

We are not yet using Dynatrace for dynamic microservices within a Kubernetes environment. We are beginning to play in that arena. We're looking at tools that will help us migrate from our current VM architecture to a Kubernetes deployment architecture, to enable us to get more into a no-DevOps type of environment. But today, we're still on a virtual machine deployment architecture.

Similarly, we have not integrated the solution with our CI/CD and/or ITSM tools. That is on our roadmap. As we migrate and transition into a no-DevOps and continuous improvement/continuous deployment operation, we'll begin to use Dynatrace as part of our deployment processes.

The solution hasn't yet decreased our time to market for new innovations or capabilities, but we believe that we will realize that benefit going forward, since we'll be leveraging Dynatrace in our lower environments to find out where breaking points are of new features that we release.

We have half-a-dozen regular users who range from our e-commerce architect to DevOps engineers to front-end software developers. My role as a user is more of a senior-level executive or sponsor role. We also have some IT folks, some database administrators and some CI people, but most of our users are in the IT/technical realm.

We don't have a team dedicated to maintaining the solution. We do have a team responsible for it, though. That is the team that just helped instrument our lower environment with Dynatrace. We've got some shared responsibilities and some deployment instructions that are shared across three different groups. They're from IT, our omnichannel group, which is really our business side, and we leverage a third-party for staff augmentation and they use Dynatrace to help us monitor during our off-hours.

With Dynatrace, my company pretty much utilizes it to try and catch performance issues before certain issues get created on our online banking platforms, as well as for technical performance issues in our internal systems and to make sure that our users get the best experience. The aforementioned details consist of three use cases. Obviously, my company stopped using some of Dynatrace's features since we started getting a few issues as certain services have gone down or been degraded. With Dynatrace, my company receives pop-ups on our site in terms of an alert to which we can react if needed, and it helps us minimize any negative impact on our clients or business stakeholders.

With Dynatrace, I think I like its ability to dive deep down into each service and application at the code level. You can see Dynatrace interacting with other applications, so it gives you a good understanding of where things go wrong. I think it is just that Dynatrace gives you great observability on your platform.

With Dynatrace, there is nothing that I would like to see improved in the product right now. Dynatrace pretty much fits in and meets all the checkboxes or requirements of my company. I know that a new product from Dynatrace will be launched soon, and my company may plan to move to it, so I think all the requests from my company's end related to Dynatrace may actually get covered in the new product.

From an enhancement perspective, I would like Dynatrace to focus on areas related to cognitive AI since it can help its users better understand their problems. With AI-related enhancements in Dynatrace, I can talk to the tool in English. Instead of getting some codes from the tool, Dynatrace can tell me the problem in a normal and understandable English language. If I am not mistaken, the aforementioned AI-related area may actually be released in the new version of Dynatrace.

I have been using Dynatrace since 2013, making it almost ten years.

It is a 100 percent stable solution.

Dynatrace is a highly scalable product since it is a SaaS-based application. As it is a SaaS-based application, you can deploy ActiveGate wherever you need it or closest to your environment.

Though I cannot check the list of the users who use the solution and don't have access to see the number of old users, many people use the solution. It would be close to around 300 users presently who use Dynatrace.

The solution's technical support is extremely good. If in our company, we are stuck with something, Dynatrace's technical support team is always quick to respond, and they always have answers to our questions.

I rate the technical support a nine out of ten.

Positive

I have experience with SolarWinds and Applications Manager from ManageEngine. I predominantly use Dynatrace.

The pros of Dynatrace are that you are able to drill down to see in-depth how your application is performing, how your host is performing, and how your business services are performing, right from the cloud level down to the codes. The con of Dynatrace is that, at times, because it has so much information, it becomes difficult to see the root cause of your problem, and then you have to dig around to find the root cause.

The initial setup of the product is a relatively easy process since it is a SaaS-based platform. Previously, with Dynatrace, my company had it deployed on an on-premises model. Currently, when my company deals with the setup processes of the product, it is really easy since you just install the agents on your server or on your hosts, after which the product starts to do what it needs to do, and then you can just create your dashboards and alert systems. If you understand the application, the setup phase is a really simple process.

The solution's deployment and maintenance processes are handled by a team consisting of four members for both South Africa and the UK, and they also readily function as a support team. In terms of deployment and product administration, you can know how to utilize the tool from a much broader base.

Owing to the fact that Dynatrace is a SaaS-based product, there isn't much maintenance required. My company only subscribes to the services provided by the solution, and Dynatrace looks after the maintenance part, a major reason why only a small team is required to administer it.

I recommend Dynatrace to those who plan to use it since it is a Rolls Royce of monitoring tools with which you can't go wrong. Dynatrace gives you exactly what you want. There are no comparisons to Dynatrace with any other tool out there in the market.

Dynatrace is a brilliant product.

I rate the overall product a nine out of ten.

The primary use case is for application performance management. So, we are using it to identify outages of different parts of the application as well as how we can make the application more efficient and rightsize it.

We can see down into the layers, such as with databases. We can see database queries which are causing problems. 

We can see CPU usage for different containers. I can do a run and see what errors exist in containers which are causing problems. We can rightsize containers on the fly and understand what is happening with our Docker, microservices, etc.

The most valuable feature is it has AI in it. The artificial intelligence (AI) engine in it is able to do alerts and some good analytics. During outages, it is able to identify and correlate where the actual root cause of a problem is. This connectivity allows us to be able to see a bit further into the application down through the layers. If it is a problem within AWS, a problem within a container or something that a user did. We are able to see and coordinate that, then we are able to tell the developers how to fix it.

The GUI has the most room for improvement. Sometimes, it can be a little cumbersome to find things and be able to create your own views, or be able to dig in and understand where things are.

Some additional features would be the ability to break out some of the permissions and allow some additional or different ways to tag services, events, and different things which run. We want to push down the ability to do that, so developers and other folks can get in there. Currently, more permissions are needed to be able to do certain things, and we want more people to be able to use it, own it, and understand it.

We don't put very much stress on it. We could probably stress it some more, but we don't have enough systems right now on it to stress it. For the most part, the ships don't cause as much stress. 

We are going to have it on about 40 ships around the world which will run it independently of our AWS platform. Those are don't stress it too much. We will probably stress it at a certain point, along with AWS, but we still very much growing the platform.

It can scale very well and very high. We don't need it to scale as much right now. It is able to absorb a lot of the systems that we have with the agents and and the API Gateways. It seems like it can scale very well when we need it to, so scalability is good for us right now.

If we needed technical support, we usually call our account team to help us figure out where the errors are, whether it is something with an agent or management servers.

It is pretty easy to integrate it into the AWS environment. You give it a username and password and it asks some basic permission. It can pull a lot of information very quickly. We are able to correlate more and provide more data for it. So, it was easy to integrate it into that environment.

We have it running on AWS. It integrates pretty well there. We have it on Red Hat Linux servers, as well as Windows servers. We have it running on VMware where it integrates very well. It understands these productions and understands our platform. It is able to read into Docker containers and all the databases that we run. However, it is limited as far as how many of a certain type of database that we can have, but for the most part, it runs pretty well and integrates very well.

It has been doing a good job of alerting us to issues. It has been very helpful and effective at identifying how we can do things to make our infrastructure and application a little better.

We considered AppDynamics, Datadog, and Crashlytics. We even considered things like Splunk for different pieces of it.

We chose Dynatrace because we needed something which could run both on AWS and VMware on our ships that might lose their Internet connectivity. This product gave us the flexibility of being able to do both. Dynatrace had the ability to run independently, so we could access it while it retains information.

A PoC is the best way to go. Put it against an application and go through the paces of tagging, analyzing, and alerting on it. You can understand what it does and how it does it. Give it a very complex application, so you can see how well it works.

We use the on-premise version because we have it running on VMware. We also use it on AWS to manage our systems on AWS for production and for our non-production environments.

We have hundreds of applications in our organization which are currently instrumented. We define business transactions and provide real-time monitoring for these applications.

Overall, I'd say we're pretty satisfied. However, as a larger corporation - our environment is very, very large, we have over 15 production servers and a total 20-plus Dynatrace AppMon servers - it's increasingly difficult to manage as our environment grows out. It's simply because our team is not fully staffed to support such a large environment, and to do the maintenance work with all the upgrades from 6.5 to 7 to 7.1. We have some challenges where our hardware that we are using today is hosting one servable host with two different Dynatrace AppMon instances, which is not, I guess, a typical setup. So sometimes it's a little bit challenging with the support, but we work through it.

As an administrator for the AppMon servers, we see the benefits every day when we help business teams to figure out some of their problems, troubleshoot to root cause. When we hear of these cases where we save business teams or application support hours or days of figuring out problems, that's probably what we're most proud.

Definitely HA, because we have so many applications that are dependent on AppMon that it has been deemed critical. Any downtime, it just affects so many users. So that's one of our key asks for the future.

Stability is where the "fairly satisfied" comes in. I think it's also due to our environment and having multiple servers hosting dual instances of AppMon, where we've seen a few challenges. We do work with the vendor. However, because we've had instances of down AppMon servers, although we can recover fairly quickly, one of the key pieces that is missing is having high availability. I believe it's coming in 7.1, so it's on the roadmap, we just wish it would be sooner.

As an organization we keep growing, because everybody wants AppMon. Even within my last two years, since I've joined the team, I think we've added four new production servers and probably eight to 10 including dev and QA. However, instead of having two very large Dynatrace servers, we had to scale out laterally. 

We've had challenges. I would say it's not scalable, because we've had to move large applications that were in a shared environment to their own separate Dynatrace server instance. Those are some of the challenges we do have.

Support has been very good. We are in constant contact with our sales engineer. 

They're very responsive, and anytime we do have an issue and raise a concern, we get immediate feedback. We have a good relationship with Dynatrace.

I was not involved with the initial setup. But since I've been there we've upgraded from 6.3 and 6.5, and we're currently rolling out, I'd say, 90% of our environment is at 7, we're just missing one server. I would say the upgrading is fairly straightforward. It was just a lot of work, due to the size of our environment.

When it comes to the nature of digital complexity, and role of AI when it comes to IT's ability to scale in the cloud and manage performance problems, that's the direction that we're already going, and I don't think we can avoid it. It's something that for us, as a large organization, we will need to leverage. I think we will adopt it, hopefully, sooner rather than later.

If we had just one solution that could provide real answers and not just data, the immediate benefit would be that we'd be able to do more work, free up our time to do other tasks. Also, as a trickle down effect, the more time we have to do other people's requests - we have hundreds of applications in our organization  - so the trickle down effect would benefit all teams.

For us, the most important criteria when selecting a vendor are stability of the product, and HA is definitely on the list due to our nature of our business. Also, new features being added on, that's always a big plus.

I would give it a solid eight. Again, it has a few features lacking or which haven't been there since the inception - the HA - because we've gone through three or four upgrades. When we lose our one server, we might lose two server instances, so it affects more applications.

I'd definitely say sign up for the trial, test it out in your test environment, and get your business users and app support teams involved quickly just to see the benefits. Just being able to look at the PurePaths; the first time I saw PurePaths I thought, "Wow. This is a pretty powerful tool."

Our primary use case right now is that we are dealing with the perfect days and non-perfect days.

We have a certain goal. E.g., for this financial year, we want to have 350 days of perfect days. The perfect days is where every application in the business should have low business impact, all applications should be available, and there are some other metrics that we want to know. 

We have constraints whether this is a perfect indicator, and saying whether it is a perfect day or not. There are some situations where one of the JVM is down, but the other processes, which do the same thing are up. In this case, pretty much there is no business impact. However, there is a technical issue, though no business impact. We can't sell this as a non-perfect day. Yet, it is a perfect day. 

Right now, we are using AppMon. Therefore, we are using AppMon to find out what metrics are available for us to see or indicate what is a perfect day or non-perfect day. That is one of the things. We are also using reactive stuff more for reactive stuff at the moment.

We are using AppDesk on user experience in indexes for customer satisfaction. 

We have been using for almost one year. It has been performing well.

The most valuable feature in AppMon is the PurePaths. Previously, we did not have this feature. The transactions using PurePaths are a good thing. 

We have like different teams like in a cross structure (DevOps, infrastructure, IT, product monitors, and developers), who recently joined the team. They are not aware of what are the missions their touching and what are the other components or services that they are depending upon. Because of all this, it has been very helpful for the developers who just joined the team. It can be explained, "Okay, this is our application. These are all the components that we are touching. Changing any of this might affect all these structural things. If we want to do any changes to this, we might need to put all this in our test cases, then QA it just to make sure we are not corrupting it."

In AppMon, the performance could be improved. That is the one thing I am most interested in. 

The other thing is the database. They might improve the database stuff a little bit more. The metrics and whatever that they are providing for database.

AppMon is lacking the AI that can be found in Dynatrace Managed.

Maybe last year, we had issues interacting with the MQs and the mainframe. They completely resolved this issue in 6.5, so we are now good.

We do not have downtime using Dynatrace.

It does scale well. 

Right now, we have some performance issues with Dynatrace AppMon, but the AppMon team is working closely with us registering the number of issues we are having and providing an extra set of tools that helps us to make the performance of the tool better.

One of the performance issue is when we are trying to bring up user data, such trying to bring up 20,000 or 50,000 PurePaths. That is where it is taking like five to seven minutes. When we are on a call, we do not have that much time. We want to make it approximately less than two minutes. They are doing a great job on that.

I would rate the technical support very well. They work with the inside their development teams to get us the best answer, as much as possible.

We have LoadRunner and Wiley. Our company has used Wiley for 13 years. 

They are one stop tools. If there is an issue, we have a team that always is on call: One should come from infrastructure, another from the data side, another from the product AVR, another from mainframe, and one person from Wiley saying, "These are the threats we have and open systems." So, we have five different people on a single call for a single issue. Sometimes we have 10 to 15 people on the call to figure out the issue.

With AppMon, looking at the translation flows and the PurePaths, we can with one or two members can identify and start to find where the problem is. So, this is a good feature.

The initial setup was straightforward.

We did have technical support help. During the first year, they have given us a resource, who has helped us in setting up the Dynatrace: getting some applications onboard, how to set up on dashboard, etc. This has helped us a little bit getting more familiar with the app and getting up to speed.

We have some demos on the Wiley, but they came very late to the table. Also, Splunk ITSI reached out to us.

For 13 years, we have been using Wiley. We definitely liked seeing the PurePaths being more helpful for us. As to Splunk ITSI, there is more configuration than AppMon. That is the reason we chose AppMon.

If you are implementing it for mainframe or MQ stuff, what are the things available and what are the other configurations that you need to set up.

Right now, we do not have AI capability. We are on AppMon. For us, it is about going and debugging the PurePath and looking into what is the issue: finding out the other use cases or root causes. It is pretty much manual. We are trying to moving from AppMon to Dynatrace Managed within the next six months. We are planning to do a debug on that. Going through all the videos and classes, it seems like Managed makes more sense for us and would be more helpful than AppMon.

If I had just one solution which could provide real answers, not just data, the immediate benefit for my team would be escape being pulled into a call and spending most of the time in analysis finding the root cause. If we are able to find the root cause and fix it immediately, that downtime would be less. That is the biggest benefit.

Most important criteria when selecting a vendor: customer support. That is most important, because companies do not have the tool knowledge initially, and someone needs support it or they need to hire someone. For companies like us, initially we onboard someone who has much more experience with the application inside the company, because we need some training on the customer support: when to support and what we need to do. 

The next one is writing the PoC, we have to find out whether it is satisfying all our use cases. So, if a system helps us with our issues, that would be great.

The primary use case is performance, capacity, and availability management along with user experience monitoring of 20 systems on a variety of technology stacks. User experience monitoring and optimisation of system performance and workflow. It has created good visibility on these topics for audit and compliance purposes, supporting adoption of a DevOps culture and practices within the team. 

We have FACT, COLLATE, and CODIX iMX technologies as well as in-house developed Java and .NET applications. These are hosted on Windows and Linux OSs and primarily on SQL Server and Oracle RDBMS. 

It has created total transparency between technology and business on all aspects of systems and performance as well as being a proxy for network performance through user experience monitoring. This followed a major performance degradation of our primary frontline system, which highlighted inadequacy of infrastructure focus tools, e.g., Nagios and Zabbix. It helped detect and remediate several performance issues on systems on both vendor supplied packages as well as in-house developed systems. It also improved InfraOps and development teams understanding of system behaviour and performance characteristics.

• AI
• Auto-discovery
• Automatic baseline
• Synthetic monitoring
• Log Management
• Drill-downs
• Root cause analysis
• Apdex
• PurePaths make system management simpler, better, and faster. 

I would like more flexible data export functions and APIs. The end user experience data is very useful to the solutions team to determine actual system usage and misuse. Flexible, easier data APIs would allow us to export the data more easily to other analytics platforms to enable this analysis as well as enable storage of this data for longer term analysis since DynaTrace only holds user data for 35 days.  

When we use the Dynatrace API to extract the data it only allows for 5000 records or less, and the data is not sufficiently granular for our needs. 

Dynatrace can be configured to continually send user session data to a HTTP Webhook endpoint. Our user session export sends JSON data for all monitored user sessions to the configured HTTP endpoint(postgresql db).

The data is sent in bulk to improve performance, with a flush every few seconds to keep the data rate near real-time.

The data format is one JSON document per line, so we must split the data by line to get valid JSON documents.

We are raising an RFE with DynaTrace to have this data more easily accessible via API

Nine months.

It is very stable with frequent updates and feature expansions. 

It is very scalable. Agents limit its own consumption, no longer impacting server hosts.

Our experience was very good. Online help via in-app chat was very helpful. Excellent webinar and online training was provided.

A host of open sourced tools, which could not get beyond basic infrastructure resource monitoring. We needed APM and UEM.

It is easy to get the basics, but more complex when you want more complex metrics and dashboards. E.g., we mapped IP addresses so we knew which corporate campus end users were connecting through it.

We used both. IT Ecology was the vendor. They had excellent knowledge and were able to transfer knowledge to our staff.

Good.

It's more expensive than other solutions, but worth it. We use full APM monitoring on our primary systems, but only resource monitoring on lesser systems. We shift licenses around our environment when a deeper dive into lesser systems is required.

We did not really evaluate other options. AppDynamics could do the job, but we had access to an experienced Dynatrace service provider which enabled us to accelerate implementation, rollout, and knowledge transfer.

Anecdotally, it is not as user-friendly as AppDynamics when it comes to configuring dashboards, etc. However, I do not have personal experience with AppDynamics and cannot say for sure.