What advice do you have for others considering Dynatrace?

Technology keeps evolving. In my experience, we recently migrated our application from Azure VM to microservices hosted in Kubernetes. Some requirements were there, especially with GCP. Using the solution does not depend on the company size but on the requirement. Whoever uses an e-commerce ordering website must have Dynatrace. I would recommend Dynatrace to other users. Overall, I rate the solution a nine out of ten.

The value of Dynatrace is in its observability feature, but understanding the pricing model can be intricate. Ensure you have a good grasp of how the consumption-based model works. I'd rate the solution nine out of ten.

Dynatrace has an AI engine. It collects numerous metrics from the customer's IT environment. The AI engine then correlates and analyzes all of these collected metrics and transactions to offer some capabilities to the customers. However, my recommendation depends on the use cases or pain points for the customers. For application visibility or end-user experience, I would recommend Dynatrace. Overall, I would rate the solution a seven out of ten.

Our clients are enterprise businesses. Dynatrace's integration capabilities are good. I rate it a ten out of ten.

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.

It’s definitely a good tool. It is a perfect combination of technical and business. It enables us to identify and make dashboards related to hardware, application, and business. Overall, I rate the tool a seven out of ten.

I would say to go for it. You won't regret it. Dynatrace has been an awesome product. The complexity of Dynatrace arises from its vast array of features and settings. It takes a considerable amount of time to learn and understand all the options it offers. Overall, I would rate the solution a ten out of ten.

Our deployment model is on-premises. I would rate this solution as a whole a nine, on a scale from one to 10, with one being the worst and 10 being the best.

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.

I am just a customer and an end-user. I'm using the latest version of the solution. It updates regularly. I'd rate the solution eight out of ten. I'd advise users to try it out. However, it's more for large-scale companies and not really the best for smaller organizations.

At the moment, I'm using Dynatrace. More than fifty people use the tool within the company. I'd tell anyone planning to use Dynatrace for the first time to review the tutorials and check how to analyze data on the tool. I'm giving Dynatrace a score of eight out of ten because it's not easy to understand the tool entirely if you're a first-time user. I'm a Dynatrace customer.

I would advise others to fully explore Dynatrace because it is more expensive than other tools. It is important to educate yourself on the solution to fully understand if it is suitable for your business. Not understanding this upfront, could cost you more money in the long term. I would rate this solution a five out of ten.

In this solution, they try to take a whole lot of complexity and make it look simple. It is not an easy thing to do. There is a release every month of new features. They are pretty good at implementing things when you log a feature request or enhancement. The vendor is running DevOps and has a high frequency of releases, so you don't normally have to wait for the next major release, provided that there is enough requirement for it. Quite a lot of the new design in the new version has been influenced by the new privacy rules in Europe. They've had to restrict a lot of what can be seen, in terms of the user's personal data, which can be seen as a good thing. Generally speaking, they've gone from a very open design where you can see all of the database queries and the data, to a more closed system. You can still find that stuff, but you have to turn on a lot of things and implement them. They are not there by default. I find this a source of frustration because some of the time, the problems are because of the data. For example, someone put in their name wrong or put in an apostrophe. Without seeing the data, you don't know and can't figure out what is wrong. You have to figure it out by looking at it. This is a GDPR thing, however, and it is necessary for compliance. Companies have to decide while consulting with their customers, how much people are allowed to see. Then it can be configured. My advice for someone who is implementing this solution is to take some time to plan out your operational environment in advance. Try to maintain consistency in naming, because I think that you can get additional value through this planning. You can roll out ad-hoc and it will be fine, but if you take some time to name things then you can get a better picture of your environment. This is a very good solution, but nothing is perfect. I would rate this solution eight out of ten.

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.

I'm working with Dynatrace. I'm using an older version of the solution. Within the company, eight people use Dynatrace. The solution is straightforward to maintain. Even if I have three and a half years of experience with Dynatrace and a total of eleven years of experience with other APM solutions, my only advice to new users or anyone looking into implementing Dynatrace is that it's a good tool. However, I still need to dig deeper into the solution to give more advice. My rating for Dynatrace is ten 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.

I would recommend following the instructions. It's easy to understand. Nothing is very perfect. I would rate Dynatrace a nine out of ten.

My advice would be to try it before you buy it. I would rate it a strong eight out of 10.

I rate Dynatrace a ten out of ten.

Over the time that I have used this product, I have worked with several versions. I am now working on the latest one. The advice that I typically give to my clients is that you shouldn't think that it will do everything. In order to implement it properly, we need to clearly understand what are your specific use cases are, and then work on those. Use cases can be related to an environment, a technology, or a platform. If it's a cloud-native service, for example, then you won't be able to use Dynatrace because it can't even be installed. You won't get anything out of that. This is an example of how it is not suitable for every situation. The feasibility depends on what you want to use cases are. I would rate this solution an eight out of ten.

Dynatrace is really good at keeping some infrastructure details and really good at the application level. I would give this solution a score of ten out of ten.

I rate Dynatrace a nine out of ten. I would definitely recommend Dynatrace, especially if the customer has a big budget. An enterprise company should purchase Dynatrace, even when compared to other APM solutions like New Relic.

I would rate this solution a 9 out of 10. It's not a 10 because there are some little things that could be enhanced. Otherwise, the product is great.

It is the best solution in the market. I can't believe the people classify it at the same level as the other leaders on Gartner Quadrant. It is way advanced than anything else. You can't find anything that is exactly like this. I would rate it an eight out of 10 because it is just missing the network management interface integration. I would rate all other solutions that I've seen a six out of 10.

We're a customer. We tend to use the most up-to-date or stable version of the solution. I would recommend Dynatrace as an application performance management tool. It does its job quite well. I am able to see a wide range of the application I'm looking at, and what other applications it is interacting with. We do get quite a lot of information, which allows us to better understand what's going on. I would recommend exploring an IPM tool. I haven't used one of the IPM tools yet. I'd be interested to see how it handles a security event or security incident and event management. That is a bit of a gap for me at the moment. I'd love to know if it does that. There are other tools available, however, it is kind of nice to be able to sort of stop in one spot. I need to learn more about the tool. I was kind of running up against my limitations with the tool, rather than the limitations of the tool itself. I'd rate it seven out of ten, simply due to the fact that I still need to explore it more.

We are an IBM partner and are beginning to work with solutions such as Instana as well. We're also partners with Dynatrace. In the last three years, we've started to grow our customers and have new use cases. I believe due to the movement towards digital transformation, we have more opportunities to show the benefits of a platform like Dynatrace. We are using the private and public domain from Dynatrace, however, we have customers and major financial customers who prefer to use either private clouds or a private environment. We believe that it doesn't matter where they are. I'm happy with this model, as we could get faster results in two weeks when we are implementing Dynatrace to our customers. It's faster to implement on the cloud. I'd rate the solution at a nine out of ten. We've been quite happy with its capabilities overall.

You need to plan how it will be consumed within the company and assign a product owner to make sure uptake is there. We have 100% adoption. Everyone who needs to use it, uses it. I would rate Dynatrace as a nine out of 10.

I would absolutely recommend this solution. There is no better product on the market. I love Dynatrace. I might be biased, but I would give it a nine out of ten.

I recommend this solution to others. I rate Dynatrace a nine out of ten.

If you're not working within real big enterprise environments, then it's a nice tool to implement; however, if you have a huge assignment enterprise, then I think Dynatrace is not suitable and would be expensive. Overall, on a scale from one to ten, I would give this solution a rating of six.

I rate Dynatrace a ten out of ten.

We are partners and implementors. I'm using the latest version of the solution. I'd advise others to plan the requirements well and be aware of integrations that could be more complex. Training the operational team well is also important. With a good operation team, you can take advantage of the tool in many ways. In general, on a scale from one to ten, I would rate the solution at a nine.

If the price were reduced then we would use this solution again. For those who are interested in using this product, we would recommend it. I would rate Dynatrace a nine out of ten.

As we're using the cloud deployment model, we're consistently on the latest version of the solution. We are a reseller. We both use it ourselves and offer it to certain clients. The best thing you can do is try it. You can try it for free. You can try it in an environment you know really well. That way, after a trial, you can decide if it really will work for your company or not. On a scale from one to ten, I would give the solution a solid nine.

I will continue using Dynatrace and I can confidently recommend it to others. I would rate Dynatrace a nine out of ten.

I would recommend this solution. In Georgia, it is already very popular, and many companies are using it for applications and external channels. I would rate Dynatrace a nine out of ten.

I would recommend this solution to others. We plan to keep using it. I would rate Dynatrace a ten out of ten. It is perfect.

I would rate Dynatrace a seven out of ten.

We're just a customer. Only a few of us are using the solution. We're currently evaluating the solution. I believe we are using the latest version of the solution. Aside from the pricing, which is quite high, I would recommend the solution. I'd rate the solution nine out of ten.

Anyone looking to implement this tool needs to take a 360 degree approach. If you take that approach then everything will be easier because you can see all the stakeholders and the value that the tool can give. If you approach it from only one angle, such as from the developer or operations perspective, then it would be very difficult to get an idea of all the features that the products has. This tool is very complete, but the price can become a bottleneck for some. I would rate this solution an eight out of 10.

Without a doubt, I'd recommend Dynatrace for business critical applications and anything that's driving revenue. Biggest lesson learnt: To recognize the most value from the information that Dynatrace provides, you need to make it available to everybody in the DevOps group. There is a wealth of data which can be exposed, manipulated, and consumed by other systems, not just what's visible in Dynatrace. This can also be used for inputs into other upstream platforms. Understand the demands within your environment and plan a pipeline, then discuss with Dynatrace. We're aware that there are use cases for notifications that can be used for triggering self-healing or autoscaling, but we are not using those yet. I would rate this solution as a nine (out of 10).

We do not use the solution for dynamic microservices within a Kubernetes environment. It was on our development roadmap for this year, but I think COVID-19 has probably pushed it to next year. While it is something we will be doing, we're not doing it now. We have not yet integrated the solution with our CI/CD and/or ITSM tools, as it was on our roadmap for this year. We are a GitHub and Jenkins shop, and Dynatrace has plugins for both of those tools. One of the very next things we want to do with the tool is plug it into our CI/CD process so we can have sort of a hands-free built. We want to allow our builds to run through the entire pipeline and be managed by these three tools, then allow Dynatrace to do the reporting on the deployment and the resulting difference in the web application based on that new format. My advice would probably be to start with the SaaS implementation to get a feel for Dynatrace, what it does, and what it can deliver. Then, based on results with the SaaS platform, evaluate installing the onsite on-prem solution. They both have their advantages and disadvantages. They obviously work best when you use them together, but there are some instances where our firm does not need an on-prem solution and may need just the SaaS application. Vice versa, there may be some firms that just need the on-prem solution and don't need the SaaS cloud based solution. In my opinion, it is best to start with SaaS, then based on what you discover with SaaS, decide whether you need on-prem. I would give Dynatrace a solid eight (out of 10). It's beyond the expectations that I had when we purchased and installed it. As I went along and learned more about Dynatrace after the implementation, I was impressed with how much the tool does. Another aspect is not just how much it does, but how easy it is to do it. The AI engine runs 24/7/365, providing input. The dashboards make it super easy for my users to use as well as myself. The analytics that it provides are very easy to read. You can present them in pie charts, bar charts, or single table data. There's just a myriad of ways you can display the data that you get from Dynatrace to make it more consumable for users.

I've been doing this for close to 30 years. I've worked for software vendors and I've worked for major companies and now I'm at this small healthcare organization. The "holy grail" has always been the ability to decompose response time and Dynatrace has done that and integrated all of my APM needs in one tool. That is the biggest benefit to me. I can do application performance, from web to Java deep-dive, in one place. That's probably why it costs so much. If you're thinking about Dynatrace, consider how easy it is to install and maintain. It has broad coverage and it's easy to use. I don't know how the rest of the market even competes anymore; it must be on cost. As an APM tool, I'd probably rate it at nine out of ten. There are a few rough edges, but I think that's mainly because they're trying to do the right thing too fast.

The biggest lesson that I have learned from Dynatrace is that application performance monitoring is very complex, but the easiest part of it is the technical aspect. The more complex thing is all the internal company politics around it. We see a lot of data and if you are targeting some people and say, "Hey, your data bridge is going slowly," they will respond to it very defensively. If they have their own monitoring tools, they can say, "Oh no, my database is going very fast. See my screen is green." But we have the insights. It's all data, and gathering the data is the technical aspect. That's easy. But then convincing people and getting people to agree on what is obvious data is far more complex than the technical aspects. The way to overcome that is talking. Communication is key. I'm a little bit skeptical about the self-healing. I have heard a lot about it. I have gone through some Dynatrace instances where they have this self-healing prophecy. I think it's difficult to do self-healing. We are not using it in our company. There is a limited range of problems that you can address with it. It's only if you definitely know that this solution will work for this problem. But problems are always different, every time. And if you have specific knowledge that something will work if a particular problem arises, most of the time you can just avoid having the problem. So I'm a little bit skeptical. We are also not using it because we have a lot of governance on our production environment. We cannot immediately change something in production. We are using dynamic microservices within a Kubernetes environment, but the self-healing is a little bit baked into these microservices. It's a Docker Kubernetes thing, where you have control over how many containers or pods you want to spin up. So you don't need an extra self-healing tool on top of that. In terms of integrating Dynatrace with our CI/CD and ITSM tools, we are working on both of those directions, but we are not there yet. We have an integration with our ITSM tool in the sense that we are registering incidents from Dynatrace in our ServiceNow. But we are not monitoring it as a component management system. We are not doing as much as I would want to for these Quality Gates. That can be improved in our company. Dynatrace could help with that, but I would focus on something else like Keptn, or something else that integrates with Dynatrace, to provide that additional functionality. Keptn would be more suitable for that, than the Dynatrace tool itself, but they are closely linked together. For us, that aspect is a work-in-progress. I would rate Dynatrace a nine out of 10, because it has really added value to my daily business and what I have to do in performance analysis. It can be improved, and I hope it will be improved and updates will be coming. But it's still a very good tool and it's better than other tools that I have seen.

It is a great platform. We found a lot of value in setting up user session properties and user action properties, then being able to use them to identify individual problems/customers. We use that to sort of streamline the whole process of finding and fixing problems. Biggest lesson learnt: Customers do not always behave as expected. I would rate Dynatrace as an eight (out of 10).

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.

Trust what it's doing. Don't question what it's doing. If you don't understand it yet, take the time to try to understand it. Do not implement or force the old ways of monitoring onto a completely different approach, like Dynatrace. That's definitely that the biggest lesson a lot of people in our organization had to go through. Be curious and embrace the different approach. It is definitely worth it. The different approach that it does is a good one. It's different but it's something that actually works. Those guys know what they have built and what they are doing. It is partly integrated with CI/CD. We are operating a platform with our applications, but our customers are responsible for testing and CI/CD deployed into our environments. Internally, some of our teams use it. The majority of our CI/CD deployment is our customers' responsibility, and while we do provide them Dynatrace for CI/CD, we do not control how they integrate it. We are in the process of rolling out synthetic monitoring at scale to replace other tools. We are not yet using session replay, which is mostly due to data compliance restrictions. We have very hard data privacy protections. We do have customers who are highly interested in using the feature, but we are not using it at the moment. Overall, I would give the solution a clear 10 (out of 10).

My advice would be to compare and compare again. Everybody's offering free trials, and I know that they're a pain to do, but compare the products, apples for apples. Everybody's going to compare costs, but be sure to compare the functionality. Are you getting what you pay for? Are you getting the bang for your buck out of what the product is returning to you? If all you need to know is "my server's down," you can probably get by with the cheapest thing out there. But if you want to know why the server is down, or that the server is about to go down and you need to do something, then you want a product like Dynatrace. I go to their Perform conference every year, and it's amazing to me to see the loyalty and dedication from the customer side. It's like a family reunion every year when we go to Perform. I hope we have it next year. From a core-product perspective, Dynatrace is doing everything that we ever asked for. Everything that we've ever wanted to monitor, it has always been there first.

We have integrated our notification systems through PagerDuty, Slack, and our auto ticketing app. This is to generate incident records. The integrations with PagerDuty and Slack are effective. We're in the process of migrating some tools to ServiceNow. Thus, we are in the process of doing synchronization of both the events while also evaluating the CMDB integration with ServiceNow. There are some recent capabilities that make this look more attractive to automate discovery and relationship building that we're looking forward to, but we have not yet implemented. The integration to ServiceNow will be good. The desire is to have Dynatrace help DevOps focus on continuous delivery and shift quality issues to pre-production. We are not there yet. The vision is there and it makes sense with the information that we see, but we have not had the opportunity. Even though we've been using the product now for two years, we're only now just starting an effort to roll the product out across the enterprise and replace competitive products for application infrastructure monitoring. We'll then have the opportunity for that full CI/CD integration or NoOps opportunity. We will be rolling out to some highly dense environments in the near future. We haven't run into any performance issues yet. The only issue that we ran into previously is with the automated instrumentation of the product. We accidentally disabled the competitive products that teams were using as we were evaluating Dynatrace. You can get in front of yourself in rollout. We don't have the solution’s self-healing functionality integrated into the automation product. Dynatrace doesn't have the self-healing capability of restarting services. Therefore, from a monitored application perspective, we haven't enjoyed that capability yet. We are in the process of testing some parts of the session replay. We see value there and are working through understanding the auditory or compliance impacts to leverage this feature. Based on my experience and history of the products, I would rate it at least a nine (out of 10). It's been far superior to other products in its capabilities and comprehensiveness, especially across both cloud and legacy technologies, such as older technologies (like mainframes and server-based monolithic applications).

There are long term benefits in using the monitoring tool. There is also strategic value added, as is the case of transforming the internal language of the technical teams.

Nowadays, we are not Dynatrace customers. However, we want to keep up to date with product functionality in order to evaluate the necessity of changing our current solution.

Have Dynatrace or one of its partner do a PoC. You will not regret it.

I will rate the software a nine out of 10 because they are able to help solve our issues for us even though we don't understand the system fully. To make it a perfect 10, Dynatrace needs to implement the features from New Relic in the dashboard so that I can monitor my own performance. Even though New Relic is not as good as Dynatrace, I have to understand my own system. I set each parameter manually before every launch by five minutes. I would suggest to prospective buyers to evaluate both Dynatrace and New Relic to see which features are best for your company. If you are not sure about the system requirements, choose Dynatrace. If you understand your own system and know by seeing a network outline exactly what you need for support, then choose New Relic.

When learning Dynatrace, we brought in Dynatrace people to come onsite and take my team through a week long training. We did that two or three different times. They offered this type of training. They also have online training out on their community that I could set up for my team members. The effectiveness of that training was about 75 percent. With AppDynamics, they have provided some online training. The take away from it (from my team) has been maybe 10 to 15 percent. The training is geared more towards sales than using the product for what it was intended. It boasts the features and selling points of the AppDynamics product instead of the ins and outs of how to use it once it has been installed in our environment. I would definitely recommend Dynatrace. I have the benefit of having used it for so many years. It takes less infrastructure to set it up initially. It's a single agent engine. You just set the agent up and run it, then it configures itself. It goes out and finds all your processes with everything that's running, configuring itself. The simplicity of the infrastructure and simplicity of setting it up, then actually using it, along with setting up your dashboards to monitor your metrics is much better. There are more features than the AppDynamics dashboarding. I would rate it Dynatrace as a ten out of ten. At the point of where we're at with our AppDynamics experience, I would rate it as a five out of ten.

It functions well. We are getting good support. It gives us everything that we were looking from it. We use the on-premise version and have just begun onboarding the AWS version.

Kick the tires. Figure out how it fits your use case.

I would recommend Dynatrace Managed because it has more features, and go straight for the AWS version because it is simpler to manage. It can also be accessed through the browser. We previously used the on-premise version, but have switched to the AWS version, which has more features.

I want to tell people about its hybrid security capabilities. A lot of people have legacy experience with the tool, so it is valuable. They would not have to reinvent the wheel. We use a hybrid environment, so we have to use the both AWS and on-premise versions. The product is integrated with Splunk and ServiceNow. It integrates easily with them.

Try it. It is a good product. We have used both the AWS and on-premise versions. They are about the same for us.

Try it out. They are other tools on the market, but with this one, the graphical interface is what I like the best. If that is what you really want, definitely go for it.

Research into similar products. It adapts well for integration with other products in our environment. We don't use it for AWS.

Do some research. There are a lot of tools out there with a lot of features, which people have bought into it. Make sure to get the right tool for the job. When you do bring a tool on, take it for a trial run first, then see if it is giving you the value which you are looking for.

I advise that when you are looking for a new product, consider: * Features * Accuracy * Consistency

It is a very useful product. Depending on your use case, try all the solutions out, then figure out which one is best.

It is perfect for application monitoring. The integration and configuration of this product on the AWS environment is good. We are using the on-premise and the AWS versions, which are pretty much the same. I work with a product called Rancher, which integrates really well.

Dynatrace is pretty good as they are the market leaders. We started with the on-premise version. Now, we are moving onto the AWS version. From the perspective of analyzing Dynatrace, it was able to do the EMI for all our data services. It has worked out well. We have been happy with it. It can monitor your entire infrastructure on AWS. I don't see an option why you should not use this product. If you don't have AWS as a requirement, then maybe re-evaluate. Otherwise, I am confident in the product.

Make sure that you understand the scope before you start looking at application monitoring. Understand your environment. Most important criteria when selecting a vendor: * They must have support in our country, so we may be able to contact them locally. * They must be able to fit to our functional requirements up to 80% or better. * They must be able to fit into the space that we operate in, which is the tertiary educational space. * They must be able to integrate with our current systems, as much as possible.

It looks nice. The service discovery and user play are really surprising.

It has all the things an enterprise needs.

If I had just one solution that could provide real answers, not just data, the immediate benefit for my team would be less resources needed. This would streamline and automate things. Most important criteria when selecting a vendor: reputation of the vendor. We go read reviews. We also check vendor references and talk to other customers to find out what their experiences have been.

Since you cannot manage what you cannot measure, I do give the most importance to data quality. This is priceless. If you manage based on bad or incomplete data, you are leaping into the bad decisions direction. The return might just be immediate. You install it and after minutes you are getting the full data in. The other day I compared Dynatrace to another APM solution, and the other person had been struggling nine months to get the data out. When he saw what Dynatrace did out-of-the-box, he simply could not believe it. Finally, be prepared to be surprised! It is very fast pace. The Session Replay and the Augmented Reality are just two recent examples. Almost every day I get some new perspective in this field, like AIOps, and it just keeps getting faster!