We deployed it data center by data center. We grouped the application service together, then we had an offshore team sign off the health of the service before we went live. We also did a thorough testing strategy two weeks beforehand. So, we installed it on all test services and made sure there weren't any negative impacts by installing the agent.

I didn't hire any contractors or deployment services. I signed up for Dynatrace's free trial and we went to town.

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.  

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 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 used both. IT Ecology was the vendor. They had excellent knowledge and were able to transfer knowledge to our staff.

As implementors, we can handle the installation for clients if they require it.

I was involved in the initial implementation.

I deployed Dynatrace, so it was an in-house deployment.

We hired some external experts from a company in Belgium, which is called Realdolmen. They really helped us in the implementation. They had experience in implementing Dynatrace for other companies already, so that really helped. And I would advise that approach. If you're doing it all by yourself, you are focusing on what your problems are, while if you are adding an external person to it, who is also an expert in the product itself, he will give you insights into how the product can benefit you in ways you couldn't have imagined.

In-house with help from a Dynatrace consultant.

We got a lot of support from the vendor. There was a lot of ongoing support from the vendor at that time.

Two people were required for deployment.

We completed the installation ourselves.

The vendor team tried to help during implementation. A lot of the struggles were not with the product. It was more with the way that we do things inside the company, so it was internal struggles from the company side. The product was always there and I could always reach out for support, if I needed additional help.

In-house.

Dynatrace came in, helped install it and then showed us how to use the product.

Our IT team is capable of handling any implementation our clients need.

I do it by myself. I'm a systems administrator. I take care of its deployment and maintenance. I build the system, and I connect the system to other systems. Any user who is trained on how to do it will also be able to do it.

The Dynatrace team helped us with the integration and configuration in our AWS environment.

We deployed Dynatrace ourselves as we have a lot experience working with it. Deploying Dynatrace depends on the environments that you run it on. Since that was all orchestrated with things like Puppet, Chef and Ansible for us, it just was a matter writing a bit of automation code that it wasn't already in place. One person was needed to do this properly, and it is not that hard of work because it applies to almost every environment that we deploy. For new services that we provide, it's done within the development teams writing those services. Therefore, there is no dedicated Dynatrace team responsible for integrating Dynatrace with services.

There is almost an API for everything. If you run it Managed, this means you have to administer Dynatrace's installation yourself. You run it and take care of some prerequisites, like sizing. Any system updates, back fixes, or upgrades to the whole cluster have almost zero maintenance. All you need to do is confirm it or let Dynatrace update itself. In the past three years, we had almost 50 updates or installations where we didn't even need to touch anything. We just had one or two occasions where an update broke functionality, and those were fixed with next update and within hours. It's almost self-maintaining.

We do have a dedicated staff for maintenance, but this team is not spending a lot of time on actually managing Dynatrace. They do the integrations of Dynatrace and other tools as well as development of custom integrations and configurations. This team is also responsible for the infrastructure and ensuring the machines Dynatrace runs on are scaled or adjusted properly. However, this is minor effort for them. We have a dedicated team of 20 to 30 SRE engineers and their responsibility is not only to Dynatrace. They are responsible for the whole infrastructure and surrounding tools.

When I first did an install, there were some hurdles. However, everything was well supported by our site rep, who came on site frequently in New Jersey, and was helping me out. It helped.

As product integrators, we deploy this product with our in-house team. We have a good set of people who are trained and certified in Dynatrace.

We had Dynatrace guardians onsite. 

We implemented it ourselves.

With our Dynatrace system, it required three servers and the program when we installed it on the servers. It was straightforward. You just clicked, clicked, and clicked as it went through the setup, then you were done. 

With AppDynamics, we are now on eight servers to make it function like it should. We are ten months into it now, and we're still trying to get it right. We have AppDynamics folks onsite to help us with it. It is just difficult to implement. There is so much to it. 

I sat down with one of their architects to decide how many servers that we needed, how they need to be spec'd out, etc., and that is what we built. Then, when we stood it up, and it didn't work, some other personnel from the AppDynamics team came in to look at it. They said, "None of this is correct. You are on the wrong this and that." 

Thus, we did not have consistent information and support from AppDynamics when implementing the system. However, it is up and running now.

In house

We used a mixed team. The vendor team was very technical and available and we learned a lot from them assisting us.

We have vendor support, and we collaborated with our vendor for its implementation.

I completed the installation myself.

We have one dedicated person to deploy and maintain this solution.

Our implementation was with the help of Dynatrace.  We wanted it to be fast and right the first time.  Success on both counts!

We have had problems with our implementation. 

The SAP Hybris Commerce side of things has been very smooth, but not the BizTalk side. Microsoft BizTalk is our enterprise middleware and the implementation has not been smooth with it. We purchased a professional services package from Dynatrace, but then the customer rep who was assigned to it was not very skilled in helping us overcome the challenges. She was a very nice person, and she was very resourceful when it came to Hybris Commerce, but not the other applications. Therefore, the engagement was not effective and I don't believe that I got the entire value that I thought I would from the professional service package, or from using Dynatrace with BizTalk. As a result, my BizTalk team has a huge resistance to implementing Dynatrace completely, and I have to convince them. 

As of now, we no longer have the professional services package.

We are a business partner, so we help our clients implementing Dynatrace.

We approached them and told them we want to try it. They were very cooperative. They sent us a link to download the software and the license. We did everything ourselves. They just came to do a quick onsite demo of how things work, but we had already figured out ourselves how it works. So, it was quite interesting.

For the deployment and maintenance, Dynatrace requires one or two people.

The technical support helped us spin it up, then we received training on how to use it.

Initially, we had technical support. As we started scaling, I did it by myself.

We implement this solution for customers. 

We've used technical support mainly for the original setup.

We had support from the Dynatrace team. They actually flew to us and we were working with the developers. We spent about a week with them understanding the product.

We worked with architects for the best way to configure our Dynatrace in AWS. We selected the managed architecture, and there are less configurations and costs of adoption with Dynatrace.

Directly implemented.

Dynatrace SaaS was setup by Dynatrace, however deployment of OneAgent was in-house and very straightforward.

We take care of our own environment. We are responsible for our performance setting environment. We place the first sensor. We do all those things.

I have heard it was great to have the consulting staff help you because you got it right the first time. 

The company that implemented the solution did not finalize the configuration properly. The solution was not monitoring everything that we wanted it to.

The amount of people needed to maintain the solution depends on the size of the environment. However, at a minimum, I would suggest two people would be suited.

In-house

We paid for a Dynatrace guardian to be onsite for two years. The guardian rocked. We really loved the guardian. If we had not had the guardian there, we would not have had an adoption rate like we got.

We implemented it through a vendor team, and their level of expertise was good.

dynaTrace supported us by sending a well-skilled consultant to do the upgrade. After the upgrade this consultant answered all kinds of questions.

You can easily implement Dynatrace by yourself. For us, it took about half a day to a day to do the whole installation and set it all up.

We implemented it on our own. We have five people for its maintenance.

We utilized account managers and expertise through Compuware to aid in any questions we had regarding implementation.

It is so easy. You would probably need technical support if you ran into issues, but it is pretty easy. The agent talks to the cloud solution right away.

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

We used a vendor team to implement it, who had a high level of expertise.

We have a team of five that does the maintenance and deployment of the solution.

We don't need the assistance of an integrator or reseller. We can handle the implementation ourselves.

We did it in-house.

In-house (myself).

We implemented it in-house with minimal support from the vendor.

Implemented in-house. Very easy.

In-house.

The product is really fast to implement and gives customers instant value. This is important, because it reduces costs on the implementation.

We are implementing software on our clients' environments

We implemented it almost entirely in-house, with some remote vendor support.

We implemented the installation ourselves without any issues or problems at all.

For the Kubernetes part, we have a good operator that takes care of updating the agents so we have nothing to do.