What is our primary use case?
The primary use case is to monitor all our applications. We are doing an eMPOWER application, which is a new project including customer engagement across eCommerce, CRM, etc. We want a single place where we can monitor all our applications that we are building. Therefore, if something goes wrong, we immediately can find out what went wrong.
We have not gone live yet. We just configured our environment and just started using it. So far, it is pretty good.
How has it helped my organization?
We have not gone live yet. From a technical perspective, the expectation will be it is going to provide quick turnaround on issues and provide more stability. Based on how we observe Dynatrace, it will provide us some insight on what we can expect.
From the business perspective, I think it is going to be a big deal. The conversion rate of people searching for a product and buying a product, these do not exist in our company right now.
We expect there will be big business impact once we properly go live.
What is most valuable?
- PurePath: Right now, we are using it for all our applications.
- Web monitoring: What we have is currently good.
What needs improvement?
Cloud monitoring is insufficient. There is something that they are introducing for Salesforce, which is called agentless monitoring that I like. However, it is not going to cover the server side of Salesforce, it is going to cover the UI side of it. So, we would prefer Dynatrace to make more partnerships with major cloud applications like Salesforce, C4C, etc. That way they have an agent in their cloud services, and we can capture the code level analysis of what is going on in the Salesforce side. Right now, we do not, so that would be good.
Buyer's Guide
Dynatrace
November 2024
Learn what your peers think about Dynatrace. Get advice and tips from experienced pros sharing their opinions. Updated: November 2024.
816,406 professionals have used our research since 2012.
For how long have I used the solution?
Still implementing.
What do I think about the stability of the solution?
Given our scenarios so far, it is pretty good. The expectation is to remain the same.
What do I think about the scalability of the solution?
The number of failures and the number of collectors servers, those look good right now and I do not see a need for increase for at least the next two years. Maybe after once we go live, once we will see the traffic, we may decide to if we want increase the scale. However, it may just be the extendability, and not a drastic change in the architecture of how we deploy the interface.
How are customer service and support?
We used the Dynatrace three month package, where I worked with a technical support person for three months and she helped in building the dashboards and exposing more features of Dynatrace. So, it was very helpful.
Which solution did I use previously and why did I switch?
In our company, we had Microsoft SCOM, but I do not think it did the job well. Once we figured out there is a monitoring system that can show us code level details, nothing came closer.
How was the initial setup?
The initial setup was challenging for us. Initially, when we heard about Dynatrace, we knew why it was so good. However, it was complex until you grasped the nuances of the product and the building blocks: what makes what, from where you can derive what, thresholds, goals, measures, etc. It took time for my team and me to get a grasp of what things are, so now we know what at least we have and have a good handle on it. Therefore, it is easier for us, so whenever there is a challenge, we have an idea of how to handle it.
Which other solutions did I evaluate?
New Relic is one company that we had in mind, but our company preferred Dynatrace. New Relic was on the shortlist. As the technical team, we sat with Dynatrace for the PoC and we were able to do the PoC for Dynatrace. We loved it, and we explained the same to the executive team. Another team did the PoC for New Relic and our executive team decided on Dynatrace.
I would recommend the Dynatrace solution. I know firsthand that it is the most proven solution.
In today's sessions, I heard more about Dynatrace monitoring. We are using app monitoring. Dynatrace monitoring seems to be much more helpful.
What other advice do I have?
Once the engine of AI is properly trained with sufficient amounts of data, it is going to be very critical for IT and it will be helpful and suggestive for the users. The only fear is that stage where it is trained, but not sufficiently, it will be very annoying. This is because it might pull up error messages, often times irrelevant. However, the concept of AI is going to be the future.
If I had one solution that could provide real answers, not just data, the immediate benefit would be that it would solve our problems much sooner.
Most important criteria when selecting a vendor: The baseline is when a user comes in, we want to know everything he does in our landscape. It does not matter whether it is two applications or 10 applications in our landscape. We want to be able to follow exactly they do.
That was the baseline we needed and Dynatrace fitted it pretty good, except there are some legacy applications, which Dynatrace doesn't support. Still, those are made as black box code. The bottom line is the traceability of any user. If something goes wrong, we should be able to pinpoint where exactly things go wrong.
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.