Datadog Reviews

After a security incident, we needed to find and migrate to a different cloud provider, and after evaluating different competitors and the skill set of the team, we decided to move to AWS. AWS also enables the team to have finer control over how our apps are deployed and how security and access are managed. By leveraging AWS's functionality, we have increased our application's security and sped up the deployment process. We've even been able to handle higher workloads due to AWS's auto-scaling functionality.

Elastic container services have improved our organization by allowing us to deploy our application. While this problem was not solved by using the elastic container service since we had a previous solution on a different provider, the ease and flexibility of deploys have greatly benefited the ops team and the overall engineering organization. It is easy to use. However, there are many out-of-the-box features like metrics and seeing task definitions that make life easier.

The most valuable feature I have found is the elastic container service. That is where our apps get deployed. This feature is really important to us since, without it, we would not be able to deploy our apps the way we wanted to and would have to use a different vendor. 

This service is also valuable to our team as we have a lot of familiarity with it and adapting to the services from our previous one was fairly seamless. 

Another feature that is very valuable for our team is the IAM. It allows us to control security.

ECS could be improved by including more tutorials for beginners to reduce the barriers to entry. It would help to ensure understanding and learning in terms of how to use a cloud provider. Besides this, there are not any other areas of improvement needed since the service is very straightforward and there is ample documentation.

I've used the solution for one year.

We use the solution for logs from all our applications. In Datadog, for monitoring logs, our team creates an automation for implementing massive logging in all our systems. Now, we are deploying it in our core systems.

We are using it to indicate issues and alert our operations team. With this, we better monitoring of our applications and logs.

However, the main difficulty is implementing the solutions in our Kubernetes cluster, separated just as logs to the specific namespace as the volume of logs is tremendous.

The solution is useful for monitoring logs. 

We can create an automation for implementing across all our systems. Right now, we are deploying it in our core systems.

The greatest value is integrated monitoring as it is able to quickly detect issues and improve our time to market.

Our main challenge is implementing the solutions in our Kubernetes cluster, separated just as logs to the specific namespace since the volume of logs is tremendous.

I've used the solution for one year. 

We primarily use the solution for security monitoring and anomaly detection.

The Datadog suite has allowed us to easily integrate log collection into all of our services and quickly detect unexpected changes in system data to declare security incidents.

The dashboards are great. They allow for the visualization of log data over time to detect anomalous behavior.

The ease of implementation needs improvement. I did not personally experience the initial deployment of Datadog in our environment, however, after some conference workshops, some of the pain points with deployment and turning on certain settings or features were revealed. I would not know how to deal with these issues (or sometimes where to begin) if I were starting from scratch.

Datadog is very easy to deploy at scale when implemented early in the deployment process and if made a deployment requirement.

We did not previously use a different solution. 

I was not involved with the initial setup. 

The solution is deployed as a SaaS.

We’re currently using logging, monitoring, metrics, APM, etc.  

We've started to use קSLOs. However, it takes a bit of time to work through those.

RUM (Real User Monitoring) has been very useful. I have used this in the past to debug problems in production, which has been great.

We also want to start using synthetics and tracing more. 

Our application currently runs in many different environments based on our customers' requirements. This allows us to see everything in one place and still filter by the environment as required, which is extremely useful. 

The solution has offered increased visibility via logging APM, metrics, RUM, etc. Going from almost nothing to something that didn’t take a lot of time to set up has been great since we have so little time to spare

As a startup, we have limited resources, and no one has enough time for anything. There are so many easy integrations and things configurable by YAML making everything easy to set up without needing a full-time employee. Just configuring monitoring solutions is very desirable. 

The APM is very useful for tracking down anything that’s gone wrong. I’ve been using it to make sure everything is working correctly after deployment, to make sure we don’t suffer performance degradation, and to track down anything that’s gone wrong in real-time  

The logs are great and necessary for any application. Before this, our solution would have been to SSH into a machine and tail log files. This is untenable for many reasons, and one of the first things I wanted to change.

The RUM is useful for seeing how real users interact with our website.

Sometimes it’s difficult to customize certain queries to find specific things, specifically with the logging solution. I’ve used other logging platforms in the past that have extensive and mature query languages, which might not be super friendly to start out with, yet they can be very powerful. I wish there was more of an emphasis on that instead of the UI-based tooling that Datadog provides. Even though it is powerful on its own, UI-based design lacks the elegance, efficiency, and complexity that something like that can provide. 

I've been using the solution for six months or so.

We did not previously use a different solution.

I don’t handle the licensing or pricing.

We did look into Splunk.

We primarily use the dashboard/metric with many tags.

It makes the system easier to debug. 

We really like the charts and visualization.

Sometimes, it takes a long time to load the dashboard if we have many charts.

I've used the solution for five years.

Our company is transitioning to using the solution for monitoring and analytic services we provide to customers. Once fully rolled out, there will be 80-100 users companywide. 

The solution's SaaS model is easy to manage and works well in single- or multi-cloud environments. 

The Saas format can handle heterogeneous or multi-language applications much better than using a combination of tools. 

Graph filters for logs need to be set manually which works well for JSON but not for unstructured logs. 

Making structured logs for high-performance applications is over our heads so we had to dump some technical streams for our logs. 

I recently started using the solution. 

The solution is stable and passed an our internal assessment.

The solution is scalable. 

We received product support through the sales department and they were helpful. 

The solution is better than what we previously used. 

The initial setup is straightforward which is impressive.

I rate setup an eight out of ten. 

We implemented the solution in-house and are continuing to roll it out. 

Licensing is based on the retention period of logs and metrics. 

I rate the solution an eight out of ten. 

We are using the solution from a monitoring and management perspective. We use it for alerts.

The solution's real-time user management and session analytics as well as the APM, are the solution's most valuable aspects.

We could easily identify the production box, and we could handle alerts.

The initial setup is very straightforward. 

It's stable. 

They have flag integrations, mail integrations, and other options as well.

We didn't do a deep analysis on this at this moment to identify the disadvantages.

We have noticed that Session Replays are unavailable on the mobile app. We'd like mobile app integrations. They could have better log reporting. That said, almost everything that we require is there. 

We've only used the solution for two months. We just wanted to understand the complexities and the benefits that we might get from this product.

The solution is stable and reliable. The performance is good. There are no bugs or glitches. It doesn't crash or freeze. 

It may be scalable. However, we haven't actually tested anything. 

We have six or seven people on the solution at any given time. They're there to handle fixes or do an analysis of logs or monitor the infrastructure.

I'm not sure if we plan to increase usage. We are not growing very rapidly. We're just preparing our environment for the upcoming year. 

We've dealt with support. They are helpful and responsive. 

Positive

We have used AWS CloudWatch and AWS inbuilt application of the features, however, we thought that it will be good to have a separate application to do all these kinds of monitoring and to have something for handling alerting mechanisms.

We are looking for the best available platforms on the market, which also would give us better flexibility while having everything come from one place. We found that Datadog is good enough for now, and we are still exploring what it can do and our options. We are not completely in with Datadog. We've been exploring it only for four or five months.

It's an easy product to set up. The integration was very smooth and they have multiple options. It was pretty good integration-wise.

The setup itself only took a day or two. It doesn't take long. 

We handled the setup ourselves in-house. We did not need any outside assistance. 

For some features, it was quite expensive. For example, APM and RAM, and Session Replays. We are using it in a very limited way and are not using it for every microservice. We are using it for a minimal budget. As we are at an exploratory phase and are doing pay-as-you-go. Once we feel confident, we will likely get a yearly license. 

We are customers.

We're working on the latest version. I couldn't recall the version number.

I'd rate the solution six out of ten. I need to evaluate the solution further. 

We use Datadog for application monitoring, to help identify errors. It is also used to monitor application performance.

It helps organizations to understand User Experience with user behaviour pattern

Helped to reduce production issues in a defined timeframe

Helped to refine UX

Datadog has a very good visualization for my complete infrastructure and network traffic, which enabled me to create a capacity plan.

This product is great because it shows you the SQL and your application request in a single view.

The error traceability is an area that can be improved. This is something that helps us to pinpoint the area where a problem is occurring. It is a function stack, and it should be showing us how each function is defined.

We have been using Datadog for the past couple of Years.

I have not worked on it long enough to properly comment on stability, yet, because it has to be tested across my other platforms.

We have not done a full evaluation yet, but given that it is cloud-based, DataDog has to be scalable.

I have not needed to contact technical support.

Positive

We were using New Relic prior to implementing Datadog. In terms of application monitoring, Datadog is not up to the level that New Relic is. It is a better product but the price is too high, which is why we switched.

Yes. It is not complex. It allows you to get a certification of DataDog prior deployment of associates to administration and configuration

Inhouse. We got our Admin team certified.

Time to resolution production issue

The price is better than some competing products.

NewRelic

This is a good product and I can recommend it to others, although New Relic is still my first choice. Datadog is my second choice.

Overall, it is a good product and my main complaint is that it needs better error traceability.

I would rate this solution a nine out of ten.