Dynatrace Reviews

We do a lot development in our company. We work with multiple servers, especially AWS and Azure. When we do these deployments and when we do these pipeline, we need to know what exactly is going on with the service and if there is an error. We need to know the root cause and where exactly the error is coming from. 

We have been using different kinds of monitoring tools in the past, such as, ELK and Nagios. This did not make much sense in a few of our uses cases. For example, there is an error in a deployment scenario, it does not show. It would remain difficult for us, as sometimes we could not find the root cause. When we switched it to Dynatrac, we could clearly see where the error is coming from and we could see the service performing well. We can also see the amount of usage, like the status. Particularly, the thing which we like about Dynatrace is its clarity.

It is clear. You can easily know where the error is coming from and the performance of Dynatrace is something which we have been really surprised with. Most of the other monitoring tools that we have used in the past have not been user-friendly, and most of the their user interfaces are terrible. With Dynatrace, this is not the case. It is very advanced when compared to other monitoring tools.

There are some cool features which they are trying to include like the tracing and the client side errors with the view. We could see the number of the problems where it is coming from, but we couldn't get in too deep to what exactly the problem is and what exactly the user is doing to see the error.

This a cool feature that they are trying to implement with video, which I appreciate a lot. It is not only that you are seeing that there is an error, you are also seeing where it is and what exactly the flow that caused the error. This feature has been announced it, and I was surprised by that, as it was exactly what I was looking for.

Compared to other tools, this solution is perfectly stable. The main feature with this solution is that you do not need to do a lot stuff. Everything is being done by the tool itself. Everything is in there for you. There is nothing much needed from your resources; it is all in there. That is the beauty with this solution.

Scalability is an important factor. At the same time, this is the Dynatrace solution we are talking about, it is really scalable when compared to other tools. We need to do a lot of stuff to make it work with multiple instances and multiple servers. So the scalability is there, but it is a headache when you do a lot of stuff and when you need to compare a lot of servers and do a lot of things. The scalability is very difficult to maintain. 

When things get reduced and the things from our side get reduced, as a developer, it gets much easier in order to scale. In this way, the solution is really scalable, and it is not difficult to get scalability with this solution. 

Regarding the customer support, they were very few instances that I have used them, but I would not say I use them regularly. I have only used them a couple times. They were really cool. They were really helpful. I got an immediate response, something not seen with other solutions. 

With this solution, you can always get in touch with support representatives and the developers if you want to, and you can get the solution directly from them. They are good about giving customer service, which I really like.

We have used different monitoring tools before when we had multiple problems. We would need to configure a lot. There are many tools needing an expert developer who had expertise in that particular tool. Therefore, we needed to have the proper resources for it where a lot of configurations were going on in, then one of the configurations failed. It is meaningless once your configuration fails and you can't find the error, or where it is exactly coming from. 

I was using ELK Stack. The thing with it is you need to do a lot of configurations where you need to maintain separate servers for each stack. You need to maintain three servers, which was a headache for us and it is also costly. You need to install agents in each server, which is the same for Dynatrace too. However, for the ELK agent installation, you need to configure a lot. You cannot just go execute a few commands and make the things work. You need to install, then configure it. It was pretty hard work as a developer, which was how we started to switch to Dynatrace, which is really cool.

Dynatrace is something which does not need many configurations. It is a just a simple way for you to install an agent in just three or four steps. Go in there in with just a few commands, and it is all set for you. In that way, Dynatrace is perfectly good for every cloud deliverer. 

I am happy with the Dynatrace solution. Dynatrace is a perfect tool when compared to other tools. 

AI is important when it comes to cloud. Every time you see a complex problem, you can't go in the server and find it yourself. You need expertise in order to do it. With the resources of a non-cloud person who has just been introduced to  the cloud, he cannot do everything that an expert does. 

With the evolution of cloud and an unattainable number of resources, such as everyone in your software company cannot be an expert with the cloud. This is where the AI comes in. It helps you a lot. It shows the correct path of what is happening.

AI is a huge, important factor, and it will be the dominating role in the coming future.

If I had just one solution that could provide real answers as opposed to just data, the immediate benefit it would provide would be to decrease the resources that you may need and not necessarily need to provide staffing for your resources to know the technology perfectly. You can reduce the cost of the training or for the things that would make a developer be an expert in the technology. So, it would reduce the cost while automating things, and it will make things work smoothly and perfectly for you.

Primary use case would be problem solving and remediation, and it's working very well.

It has dramatically reduced the time it takes to problem solve webpages and coding problems.

Being able to drill down into the PurePaths, to get to a solution.

We have a couple of one page apps that it has a problem with because it doesn't call to the server all the time. I believe part of that is taken care of in the next version. That was the biggest thing for me. That's one of the reasons we haven't really siloed up too, because of that.

I can't think of any issues we've had with stability.

I love it, I've always been a big fan of the scalability. We haven't scaled up yet but we hope to.

We used a guardian to begin with. He trained us and helped us quite a bit. I think we had him for about six months. He was wonderful.

As for siloed monitoring tools, I don't believe we used any. We did use an alert site, but nothing other than that.

We actually had a production issue on our catalog website. Dynatrace came in and helped us install and problem solve that issue right off the bat. That was our initial outing.

During the initial implementation I was just there as a bystander. We had our infrastructure guys taking care of the implementation. I was just there afterwards to learn how to run it. And if there are upgrades, we hand that off to infrastructure.

When it comes to IT's ability to scale in the cloud in order to monitor performance management, I can't really comment on the role of AI in that. I'm not involved in that as yet. We are just starting to have a cloud footprint now.

If we had just one solution that would not only provide data, but real answers, the immediate benefit for our team would, of course, be helping the code to be error free, but also speeding it up a bit.

What I appreciate most in a vendor, personally, would be performance in the product, and knowledge; product knowledge.

I would rate it a 10 out of 10, because it's easy to use. I use it everyday now.

Implement it and put it on every server. You have to have it all the way across with the network.

We’re primarily using Dynatrace for user-experience monitoring, for our Autodesk e-store as well as our Autodesk subscription management. 

The performance is really good. It’s really helping us to catch problems and find out where the root cause is.

The main time to resolve issues is coming down with Dynatrace. 

Previously, it used to take time to find out what was the exact reason, why this user is failing, what is the user's complaints. Now we can see proactively, this is the component that is failing, and we are going to fix it. The time to the solution has improved.

Regarding AI and managing performance problem in the cloud, it’s very important. We have a lot of monitoring tools. We believe that with the new Dynatrace AI, the alerts will be reduced. It’s only binding to one alert where the exact, root cause of the issue is, instead of giving a thousand alerts, spamming them with all the email alerts and services. Just one alert that says: this is the problem, this is the root cause of all these things.

The real user-experience monitoring is very helpful. We can see what real users are seeing, what JavaScript errors, what pages are very slow for them. As well, it helps to correlate the front-end users to the back-end application components, and the corresponding Method which is failing, as well. We are able to go to the correct spot and fix the issue.

The real-user replay that they demoed here at the Performance 2018 conference, it would be really good if we can get that. And the other is the self-healing; it’s currently not there. We have to forward the events to some outsourced remediation solution and then they work on the event. If they also provided the self-healing option, that would be really good.

So far we haven’t had any issues with the Dynatrace infrastructure itself. We have been using Dynatrace AppMon for the last two and a half years. We’re migrating to Dynatrace now, we have started a PoC, with the new AI etc., to experiment with it.

We haven’t touched scalability for the new Dynatrace yet.

We have called the technical support and most of the calls are returned quickly. Some of them will be a real technical problem and then they have to reach their engineering side; the support is not able to help. Those were the cases where support got delayed.

We had both experiences, unreasonably long for most of the cases, and some were reasonably long delays.

Previously we were using a third party e-store. When Autodesk wanted us to have a custom e-store, built and managed by our Autodesk development team, we wanted to have real user-experience monitoring on all the applications, performance and everything.

It took a lot of time with the initial deployment, of the old solution, the AppMon. With this one we have to check it out. We are doing a PoC. The deployment is going to be smooth and it’s going to be quick, that’s what I hear, here at the Performance 2018 conference. I have yet to implement the install to see that.

We did a PoC with New Relic. New Relic did not capture any events because of the front-end framework that we used at that time was Angular, and New Relic did not support it. We tried AppDynamics and that also did not support it. Then, finally, we went with Dynatrace.

We have used siloed monitoring solutions in the past and there were a lot of events, it was not good. We’re trying to consolidate everything into one. We’re working on tool consolidation. That’s one of the primary plans for our roadmap, for IT.

If we have a solution that provides not just data but real answers about where the problems are, how to fix them, the immediate benefit for our team would be time. We would have time to work on other development efforts, innovation things. It would save a lot of resources as well. That would be the main benefit of it. We’re spending a lot of time to get the answers. With one solution like that, it would be giving us the answers.

What we appreciate most in a vendor is their being more responsive and attending to customer problems; more customer-focused.

I would rate Dynatrace a seven out of 10, because of the issues I mentioned before with technical support.

I would definitely recommend Dynatrace, the new one, with all the new features that are being launched. I think these are not available in other monitoring tools. This is the best one. I would definitely recommend Dynatrace.

I am from a monitoring team, and we had a PCF environment that we were building. We needed a tool to monitor a PCF environment. We were looking at a couple of tools, and we found Dynatrace is a robust tool which provides pretty good monitoring for a PCF environment. That is when we chose Dynatrace.

It will definitely be a benefit. We are using other tools to monitor other environments, and we have to switch between different tools when we have to do RUM, do synthetic monitoring, or do competent monitoring. It is really painful.

This is where I find Dynatrace pretty good, because it has everything in one tool, and you can monitor from infrastructure to synthetic monitoring, RUM, then performance data, etc.

That is the way to go, when you do not have to waste time between setting up the tools and seeing the metrics. That is what all matters. We can save time and still get the work done.

We are just setting up the environment, so I have not done so much with Dynatrace. The thing that I like with Dynatrace is it goes to every part of the containers, and it brings up all the data and all the problems. The way it shows a problem on the dashboard is pretty good.

We finished our PoC. We have deployed our dev environment, test environment, and now we are still setting up our production environment. The reviews that we got from the PCF team, they are pretty much happy with it.

I need more experience, because I have not used the tool. As far as I know about the tool, it covers so much. Once I am more familiar with the tool, then I will have more understanding of what I am missing here. Right now, I need more experience.

We are still setting up the environment. While I was deploying it, it was pretty quick. Therefore, I did not have any complaints. I am pretty good with what I have worked with of the tools, and how much time it takes for the deployment. So, I am pretty happy with it

We had some proxy-related issues in the beginning, but it looks like it was a mix up between our environment and their environment. Maybe it was a lack of knowledge. However, so far, it has been good. 

Technical support was pretty good. They jumped on the call, and we spent some time with them in India, and issues were resolved pretty quickly. 

We did not use any tools before this product.

It was pretty straightforward and quick. I was amazed by it. I deployed it in six servers in 40 minutes, and that is pretty good.

We needed some monitoring for PCF. Therefore, we did a PoC with a couple of other tools along with Dynatrace. That is when we found that Dynatrace was the tool that we should be using for PCF.

Most important criteria when selecting a vendor: 

1. The capability that tool is providing. That is the most important thing, because if the tool is not providing what we need, we do not need the tool. 
2. The pricing. It should fit into our budget, because if the tool is providing everything and we don't have money to spend on it, that won't work.
3. The support. If we are not getting the support from the vendor, then it is useless. We spend the money, and they advertise that that tool provides everything. However, if I am not getting support, then I won't be able to use the tool properly. 

These three things are the most important criteria that help us decide which vendors to pursue.

The primary reason for choosing any APM solution, it comes through the interface, is to find out the gaps between the application life cycle when someone makes a transaction. Then, we will not know what is causing it to come back so late, delayed, or with latency. We just want to know the pain points of it. That is why we have chosen this APM solution. So far, it is doing a good job, except for some flaws, but that is fine. 

When Dynatrace shows us an entire lifecycle. I can go back to my document and see A points to B, then B points to C, and so on. I can then back and see that I plugged it in every box to see how it is behaving and how the product is dynamically showing the AI behaving in a single place, like on a single webpage. This helps us to see the troubleshooting points or what is hiccuping. This is where we go. We reboot, fix it, or do whatever it takes for it to be taken care of.

The PurePath is one feature, which I actually like. When I have a problem that is being detected by the alerting profiles, I just go in and see what the part is talking to, then what its dependencies are. For example, if a middleware application is behaving weird, then has to be sampled by different databases back-ends, or mainframes, we just keep looking at those PurePath to see what it is talking to rather than going back to my library or my documents to see what exactly the architecture design was. The PurePath helps me a lot.

1. To improve in Dynatrace the log analytics, this is the first thing that has to be enabled. 
2. We are using Splunk or Sumo Logic as an enterprise logging tool. We have been there for a long time, since even before the Dynatrace was. There were Splunk APIs that have been exposed, and we can grab the data from there. Dynatrace also has APIs, but they are unfriendly APIs. If they were friendly like Splunk or Sumo Logic had, we might integrate that same data on a single webpage, then start showing these internally. That would be a great help of a feature; friendly APIs.

Artificial intelligence depends upon business to business. If you take a travel industry, like airlines, not every month will remain the same as in the next 12 months. Our busy seasons would be around summer, Thanksgiving, Christmas, and New Year (two bottleneck seasons). If you come back and are replicating that scenario of traffic of those issues, or those latency of responses being triggered, it will not be the same as in the rest of the months. When we are plugging in the AI, we need it to have in mind this for each and every business, that the AI implementation should be different.

What happened was when there was an AI sneak peek to our portfolios for our company took an average of the last three months, which would not work for us. If it is taking an average of the first three months, say Jan, Feb and March. Our systems would be quiet because we are not handling our bottleneck capacity of traffic. Then, when it comes to April or May, that is where our busy business season starts. The AI takes the alerting profiles of the first three months, then tries to implement on those next three months, or the next coming 24 hours, and then it just screams a lot.

The AI should be tweaked for the last full year, like smart scheduling. That would help us.

Dynatrace solution is pretty much stable. 

Last time, when there were upgrades being made, the alerting profiles had been wiped off, then we had a gap. When Dynatrace made the latest upgrades, newest patch upgrade, or firmwares, the existing alerting profile, which says, "Call me when you see this," or "Call me when you see 10% of these," had been wiped off. Someone has to redo it again. Except that, it has been fixed in the next release. 

The scalability of the solution is good. We initially started with the first three major critical applications, which is where I was introduced to this tool. Right now, they are moving on to the top 21 applications, which is going to be good scalability. They did well.

I have not contacted any customer solution or support.

Since we are still on the warranty period, we have still Dynatrace guardians on-site. I can go in and say, "Hey, this is what is happening," and he will get me a solution, or he will say, "Hey, you are doing this wrong. You have to do this." If not, he would say this feature is not yet released, and we are going to have it in next Q release, or whatever. Dynatrace guardian is the first point of contact if I have to ask any questions, he would be the guy.

We never had a centralized application for performance monitoring tool before Dynatrace. 

Everyone has Sumo Logic. Someone has Splunk. Someone has Tealeaf. Someone has Riverbed. No one had a consistent idea of what another team was doing for monitoring solutions. When enterprise monitoring took place, that was where a centralized solution needed to come in. 

For example, if I was sending a transaction to a different team, and I called it as a transaction, but someone else named it with a Tealeaf ID. There was a disconnect in naming conventions. 

When the APM solution came into place, I now know what to call it and they know what to expect from me, so we are on the same page. This helps us in shortening down the time for triaging an issue.

The capacity planning was complex. Everything else was easy.

Our infrastructure setup has been there for quite a long time, then we already had JVMs who monitor our process. We needed to evaluate what options and what benefits were coming down on our plate, then what was a repetitive task which was already being done by other JVMs. We had to evaluate those on different boxes, different portfolios, etc. Then evaluating options were a little tough because we were already using some things and we had to do something new basically from scratch again. This took some time. After we had experience with the first three major applications, we knew what to do with the next 21. 

If I had a colleague interested in purchasing Dynatrace, I would ask these questions:

• What are you using these days?
• What are you missing? 
• If you have that missing point as well as what you already have, why not go for Dynatrace?

If I had just one solution that could provide real answers, not just data, the immediate benefit would be fixing the issues first. It takes a lot of time for us to dig back where the actual issues on the code base are, especially if it is a network or infrastructure-related. To get answers for most of it, we can fix our issues faster on a priority basis.

Most important criteria for selecting a vendor: Show me what I am not seeing. If you ask me, I am an engineer. I do not want to see the eyes on glass all the time. I want a solution which does it for me. I know how to set my thresholds and throttles. For example, if there is an issue, an exception, or a false exception which is coming in, I know my application:

• If it comes 100 times a day, don't worry about it.
• If it comes five times a minute, don't worry about it. That is the business clients calling improperly.
• If it happens 500 times in a five minute timeframe, then send me an alert.

That is the something which I like a lot regarding the synthetics of application performance monitoring. When I am not seeing and I am being called when there is an issue, which I set my own rules, that is a good idea. That is the great thing and a driving factor for having an APM solution. 

Primary use case is to triage business applications and slow performance for our users. It is performing very well for now.

We have been a long standing customer for almost seven years, and using different tool sets from DC RUM to Gomez, and AppMon now.

It helps us get to the resolution quicker, and potentially the root cause, and at least understand what is happening for future identification.

The ability to really drill into performance issues and help our application teams understand what is causing the business's problems.

AI is really important because there are so many different tools that we have, so much data being collected, and being able to really sift through just general users is difficult. Therefore, using some type of AI technology to help identify and pluck out the important parts, it is critical.

We would like to see more external tool integration, which is critical for us. We are a best of breed, or at least try to be, customer for tools. 

We would also like to see all the good data in a single view across multiple tools, so that access to integration is critical. 

This would definitely gets us going forward in the right direction.

The stability is really good for what we have experienced so far. We have not experienced any downtime with our tool sets.

I have not experienced any issues scaling with the Dynatrace tools, however I have experienced scaling issues with other competitors' tools.

Over the years, they have been very good. Because of growth and popularity, it has been a little more challenging getting information, but they are knowledgeable once we do get them engaged. 

We have used siloed monitoring tools in the past. We experience a myriad of issues from getting them configured to providing useful information, and also sometimes licensing issues. Overall, the usefulness of the tool and helping us fix problems became the issues.

We were using other competitors' tools. Now, we have been migrating from some of those other siloed tools, but we do still have a mixture of tool sets. 

We are a longtime customer of Dynatrace. We started out with a single product, then brought in a second, and the third, so over time and seeing how the value progresses, we have substituted different tool set with Dynatrace tools.

The initial setup was reasonably straightforward. It was pretty easy to get deployed, and again, getting the value in a reasonable time. 

We had someone from the vendor technical support providing assistance as we deployed.

Right now, we are migrating many of our things to Dynatrace. We have already made the selection. Other competitors fell short. Integration flexibility and dashboard reporting capabilities were some of the key issues that we looked at. 

Do your homework. Test. Do your proof of concept(s). Be thorough in what you need and defining your reasons for looking at the tools. Even though everybody likes what they see, it may not be a good fit for what you are trying to accomplish. 

The tool sets are great. They provide good information. You can always improve them with better data. 

If I had just one solution which could provide real answers, not just data, the immediate benefit would be a single pane of glass perspective for the application in our environment. We have been striving for this consistently in the last seven to 10 years. It is absolutely critical. It is where we are working to get to: A single view which is telling us the problem, what to fix, and moving us on to the next problem.

Most important criteria when selecting a vendor: First and foremost is honesty. We have been in technology, and we, among many other teams within our organization, are a much more of a senior team. We have people that have been in the industry for 20 years or so. Just tell me what the issues are. We have the technical wherewithal to know how to work through them. Therefore, being straight up, honest, and having integrity as you are talking about the tools, demonstrating the tools, not only the highlights, but also the pitfalls and things that we need to work through. Have more transparency.

We primarily use it for performance monitoring and to track down solutions to ongoing issues.

Its performance is great. We previously had AppMon, and AppMon is a little bit difficult. But we're PoC-ing Dynatrace, and we love it so far.

We spend less time tracking down what's truly a problem and looking for problems, and more time actually solving the problems.

• The ease of use
• The ease of installation
• The simplicity of actually getting data out of it
• The artificial intelligence

It's more than just dashboarding. It actually tells you when you have problems, so you don't have to go set up anything. It automatically figures it out. The artificial intelligence is by far the most useful thing I've seen.

Without the AI, I don't think we would be able to grow at all. As we continue to grow, our environment gets more complicated and there are "segmented people" who know little pieces of it. The AI allows one item, the software, to be able to understand everything and provide all the data.

To me, dashboarding is still a little bit sketchy. I'm definitely of the mindset that the problem cards are just more than enough. But when you're making that transition from AppMon, which is very dashboard-oriented, over to Dynatrace, which is no dashboards, there needs to be something in between so that business buys in a little bit. To me, setting up the dashboards is not that easy to do.

There should be something that would help transition, especially customers like us who already are heavily into AppMon. I would transition my dashboards over so that we don't have to recreate them, because recreating them is very difficult in Dynatrace. I get that they're two different systems, but any legitimate company that is doing that... 

If you're starting in one or the other, you're totally fine. But if you're porting over... My boss has to do a whole business case on why she wants to do it, and it's really hard to say, "Oh, the dashboards that you had on the team that you were using, you're not going to get over here." Or, "You have to re-create them all over again." People are going to ask questions about cost, who is going to do that. Although the tool automatically does that, business hasn't seen it yet. So it's a really hard sale. I would love to see some kind of integration so that we can say, "Okay, we transferred at least 80% of your dashboards over."

I haven't had it long enough to truthfully rate stability. We've had AppMon long enough, about two years, and that's been rock solid, minus any upgrades. Every time we do an upgrade there's some instability. When it's not being upgraded, it's perfect.

Scalability is great. My biggest concern when we first put it in was the resources that it would take up, network traffic that it might create. But it seems perfectly scalable to any environment. Even on some of our heaviest use servers, it doesn't seem to affect anything. So to me, it can be put on any environment and keep growing.

We have a guardian. We don't actually call technical support. We have somebody on-prem. He's knowledgeable and almost always available. Whenever he's in the office, he's available. Even outside the office, he's pretty available.

I was not involved in the initial setup. I took this over from my boss, and she was involved in the initial setup. I was kind of thrown into it, so I was a little worried about that. But it's been pretty easy.

I'm involved in the switch from AppMon to Dynatrace. To me, that's the biggest upgrade we've got. For AppMon, I did training courses. We did one-on-ones with our guardian from Dynatrace. Even with those, it was still a very complicated tool to learn. With Dynatrace, we picked it up in minutes. It was very intuitive. That's what I can't believe. I almost wish we didn't waste the time doing the training for AppMon. I would have just gone straight to Dynatrace.

As for a tool that would not only give data, but real answers, it would make things even quicker. I actually think that's what Dynatrace does for us right now. It tells us the answer to what the root cause is. It doesn't actually fix it, which I'm hoping it will eventually do, but it actually gives us the right answers right now. That is better than what we had before, which was somebody would go in there and try to find the problem. They may not have gotten to the root cause, so they would put a temporary patch on it, and then it would come back again. Now, we seem to be getting to the root cause every time.

Our most important criteria when selecting a vendor are knowledgeability and the future vision, which, to me, is the most important part of Dynatrace. They're not thinking about, "Here's a tool for today, and we're just going to keep improving it slightly." They already have a master plan for where they want to go, and the tool reflects it. It shows that they're just thinking way ahead.

I'd give it a nine out of 10. I think it's virtually perfect. There are some bugs in it. Sometimes things get hung just for second, and you have to refresh something. Also, they aren't necessarily intuitive, but to me, they're just going to get better over time.

My advice is, start directly with Dynatrace Saas. Don't start with AppMon. Don't do the other older solutions. Just go straight in. Even if you have on-premise, SaaS is much better to start with.

We have a critical enterprise-level project where we have seen a lot of performance issues. We tried to figure out what tool might help us solve some of those performance issues. Then we heard about Dynatrace, so we engaged Dynatrace. It's basically about solving performance issues.

In terms of performance, we're still a work in progress. I think we have made good progress identifying the areas where the problems are, and now it's a matter of just working with the different teams trying to figure out what the roadmap is going to be.

We're learning the tool. At the same time, it's also about educating folks within our organization in terms of what Dynatrace can do. And also how do we apply it? How do we make use of Dynatrace and what do we do with the information we get? How do we take that and go to the next step of implementing the changes?

At least we're able to pinpoint where the problems are instead of just saying, "Here's the results and here are the failures." At least we're able to tell them which calls, which methods were the problem, which interface. That was a huge step for us, to be able to do that. 

We are not the DevOps or the application team. We're coming from the testing side and, generally, it's challenging when you are working with an application built by a different team. When you run a test and say, "Hey! Here's your problem," unless you show the proof, you show the information, they're not going to be able to take it and make some changes to it. So the big first step for us was to identify where the problem was within the application. 

Now, it's mostly about, "What do we do about it?" You have these problems. What are we doing about making some changes and getting into the roadmap.

PurePath. We just started using it, it's been less than a year. PurePath is really helpful. 

And I'm learning now about the dashboards, and the session replay is another that was really fascinating to see. I guess AppMon probably doesn't have those things yet.

The features I'm most excited about are the AI piece, the session playback, and the fact that the deployment is even easier with the new version. Not only deployment, but the setup piece of it, I'm hearing, it's easy. I haven't tried it out but that's really encouraging.

To be honest with you, I think they have a great roadmap. And the fact that they are using the feedback from the customers to build into the roadmap, is a great feature. I have nothing in particular that I want to see.

From what I've seen, from what I've experienced, absolutely no problem with stability. Especially the ease with which it gets deployed, and also the support we typically get has been amazing. We have no regrets using Dynatrace. It's been a good experience so far.

So far we've implemented this for a couple of different applications. It scaled pretty well for us. We're about 2,000 or 3,000 users, but we'll have a better answer as we start rolling it out to more applications. So far, no issues with scaling.

From what I've seen, they're very knowledgeable and easy to work with.

We've used a variety of tools, not so much in the APM space. It was mostly about SiteScope and Wiley, those kind of things.

With Dynatrace we were able to pinpoint where the problems were with PurePath, which was something we did not have. Obviously, we didn't work with an APM solution so I'm only comparing this with a non-APM solution like SiteScope. There, it's mostly about, "Hey, here's your CPU, here's your memory," rather than pinpointing where the actual problems are, which is something that PurePath gives us.

I think it was really, really straightforward. It's the second time around. Some of the things, we did them ourselves.

In terms of AI, when it comes to IT's ability to scale in the cloud and manage performance problems, we don't have a cloud implementation yet. But, in general, what I've seen with AI, I think they're learning. The self-healing thing was really impressive in terms of, if you have a problem, what do you do about it? You get notified automatically. Then how do you fix it? Those are some of the things with AI that I thought were pretty cool.

If there was one solution that could not only provide data but real answers, the immediate benefit of that for our team would be huge. Not just telling us, "Here's the data" - there's so much data out there - but what do you make of it? What's the critical data? I guess that's where Dynatrace is headed with AI and the self-healing. That would be huge. If they can say, "Hey, here's your problem. Here's what you need to do to fix the problem." That would be significant. 

I think the solution meets our needs where it is, so from that perspective, it's a nine out of 10.

The most important criteria when working with a vendor or selecting a vendor are customer service and what type of product offerings they have. Do they see the vision of the future in terms of cloud and those kinds of things? Those are some of the things we consider very important.

To a colleague who is looking into this type of solution, I would say we have had a really good experience. If they're in a similar situation, try it out. Do a proof concept. Try it out and see if it's good for you. It may or may not be a good fit. Everybody's different. Try it out.