Datadog Reviews

We use different tools for log collection and monitoring. Using Datadog will combine different use cases into one product that will be easier to manage. 

The tools we use are open-source, so there is no commercial support. Having customer support would be ideal since we're a small team. 

Profiling would be another great feature to have. Currently, it's manual. Having Datadog would give us a standard, and we don't have to do much manual work.

It will solve a lot of our problems. We have different tools for each of them in our organization; they are open-source and therefore not very well maintained with there is no customer support. 

Having an industry-standard product such as Datadog would be ideal for us as we are short on manpower. Since this is a managed all-in-one product with readily available support, we will be able to focus on application logic rather than figuring out why a tool isn't working.

The biggest thing I liked was the combination of all the things - monitoring, log aggregation, and profiling. We have different tools for each of them in our organization and all of them are open-source. These are not very well maintained and there is no customer support. 

Having an industry-standard product is ideal for us as we are short on manpower. Profiling is another amazing feature. Currently, we rely on some open-source solutions, and it's all done locally. Having it done on Kubernetes would give us more insights and help with performance. Alerting is again a nightmare for us. Datadog solves all of these issues.

It can be overwhelming for new people as it has a lot of features. The UI could certainly be improved. Having less information with better organization could help newcomers. I haven't seen the documentation, however, a well-organized documentation would invite many varied users.

I've been using the solution for three years.

We use it to monitor and alert our ECS instances as well as other AWS services, including DynamoDB, API Gateway, etc. 

We have it connected to Pagerduty for alerting all our cloud applications. 

We also use custom RUM monitoring and synthetic tests for both our internal and public-facing websites. 

For our cloud applications, we can use Datadog to define our SLOs, and SLIs and generate dashboards that are used to monitor SLOs and report them to our senior leadership.

Datadog has been able to improve our cloud-native monitoring significantly, as CloudWatch doesn't have enough features to create robust, sustainable dashboards that are easily able to present all the information in an aggregated manner in one place for a combination of applications, databases, and other services including our UI applications. 

RUM monitoring is also something we didn't have before Datadog. We had Splunk, which was a lot harder to set up than Datadog's custom RUM metrics and its dashboards.

I really enjoy the RUM monitoring features of Datadog. It allows us to monitor user behavior in a way we couldn't before. 

It's useful to be able to obfuscate sensitive information by setting up custom RUM actions and blocking the default ones with too much data. 

I also like being able to generate custom metrics and monitors by adding facets to existing logging. Datadog can parse logs well for that purpose. The primary method of error detection for our external website is synthetic tests. This is extremely valuable for us as we have a large user base.

At times, it can be hard to generate metrics out of logs. I've seen some of those break over time and have flakey data available. 

Creating a monitor out of the metric and using it in a dashboard to generate our SLIs and SLOs has been hard, especially in cases where the data comes from nested logging facets.

I've used the solution for two years.

The stability is pretty good.

The solution is pretty scalable! It's hard to set up all the infra (terraform code) required to link private links in Datadog to all of our different AWS accounts.

They offer good support. Solutions are provided by the team when needed. For example, we had to delete all our RUM metrics when we accidentally logged sensitive data and the CTO of Datadog stepped in to help out and prioritize it at the time.

Positive

We previously used Splunk and some internal tools. We switched due to the fact that some cloud applications don't integrate well with pre-existing solutions.

The initial setup for connecting our different AWS accounts via Datadog private link wasn't great. There was a lot of duplicate terraform that had to be written. The dashboard setup is way easier.

We installed it with the help of a vendor team.

Our return on investment is great and is so much better than CloudWatch. We can easily integrate with Pagerduty for alerting.

Our company set up the product for us, so the engineers didn't need to be involved with pricing. 

The pricing structure isn't very clear to engineers.

We looked into Splunk and some internal tools.

We use Datadog for general observability into our infrastructure, as well as running analytics queries for our SLI/SLO platform. This helps all of our teams be informed of how well their products are actually performing in production, and aim their efforts at the thing that will provide the highest ROI. 

We also use it for general monitoring and alerting during load tests and service releases to detect any issues related to the deployments. This helps us maintain our high contractual uptime promises to our clients.

It has drastically reduced the amount of time we spend on debugging issues and tracking down the root causes of incidents. What might have taken days or hours with separate vendors in the past (or even single vendors with terrible UI) is now quick and easy. 

We've often gone from detecting an incident to identifying the needed fix within ten minutes or less and covered multiple domains like APM, Logs, Database performance monitoring, etc., in just a few clicks. This is extremely powerful.

Distributed tracing is the most valuable feature. We have hundreds of microservices, and knowing how top-level requests weave throughout all of them is invaluable. 

At one glance, we can clearly see which service is slow and then switch over to the infrastructure view or container view to debug why the slowness is happening. This is true of all their other integrated products as well; the more you add, the more insights you get when looking at traces.

We also use RUM extensively. This helps us cover the last mile of application performance. Without it, we wouldn't know if our browser applications were functioning slowly for our users.

There is occasional UI slowness and bugs. While the Datadog UI is generally miles above its competitors, there are a few cases where it falls short or has started to slow down over time. They also occasionally make poor UI redesign choices. They should continue focusing on this area to maintain the high standard they started out with.

I've used the solution for five years.

We've never had major stability issues.

Scalability has never been an issue, although there is occasionally UI slowness.

Support via tickets is absolutely terrible. It's the one obvious bad spot for Datadog. If we didn't have direct relationships with many of their product managers, our experience would be much worse.

Negative

We previously used New Relic. It had a terrible UI and the integration between products was not great. Datadog is miles ahead of them and is continuing to increase that distance.

The initial setup is straightforward, and the docs are done well.

We managed the implementation in-house.

Our ROI is high.

I'd advise users to negotiate rates. Datadog's off-the-shelf rates are pretty high.

We have only used and looked into New Relic.

We use the product for recording loggers on our various services across different teams. For example, we use logs to keep track of info logs for events and error logs to catch exceptions. 

When users ask us to investigate a situation, we use logs to keep track of events and where the user's code traveled to. We also use synthetic testing and monitoring features to keep track of our many alerts in the production and QA environments.

We use Datadog mainly for debugging purposes. For example, we use it to navigate where the code trace is when an issue arises due to its ability to search through the logs. 

We also use it to address user queries. Sometimes users would ask us a certain question concerning our codebase, we use Datadog to track the code stack and also use time monitoring to get an idea of the time frame around when the use case happened.

The feature I have found to be the most valuable is the filtering feature in logs. It is really easy to type plus and minus to filter out different logs. I use it to navigate the noise. 

I use synthetic tests as well. It is easy to navigate the menu and create tests. 

Much of the UI is very straightforward, and I do appreciate the ability to search for any documentation on the various features when I need to as well. The DASH monitoring boards are nice to give an overview of various performances and allow us to track use cases.

This service could be less costly. Right now, we only keep 15 days worth of logs since we want to be more economical in terms of cost. It would be nice if I had the option to monitor logs beyond 15 days. For APM traces, we only keep a year worth of traces. The UI can be a little more straightforward as well. I found it to have too many options.

I've used the solution for three years.

The stability is good.

The scalability is good.

We deploy various services for our main platform on AWS across multiple regions. We have a development environment, a staging environment, a QA environment, and a production environment. We deploy our many services across hundreds of instances. 

We have many server farms, all responsible for various services on our market intelligence platform. The deployment of each server farm or even individual instances varies depending on what stood up. We have instances built in three different ways, with two different pipelines and some even on user data scripts.

My team has a 24/7 on-call schedule where we need to be ready to handle and mitigate incidents with the platform at any moment. 

We have countless monitors set up on Datadog that alert directly to our queue using an email that generates a ticket. 

The actionable steps for each type of monitor and its associated incident are easily included in the alerts whenever something is triggered. We generate links to the Datadog monitors and can instantly drill down into what went wrong and for how long.

The features I have found most helpful are synthetic monitoring, APM, and alert features. The monitoring functionality, in general, and tagging infrastructure are great.

Synthetics have become bread and butter for us as we have migrated many tests over to Datadog. We have simplified and consolidated our synthetic tests while also making them more robust with the help of your tagging. 

A large portion of our monitoring is based on synthetics results, and alerts integrate seamlessly without an incident queue system. We use dashboards heavily. 

The metrics capabilities are extremely helpful, and we use virtually all of the widgets.

My main place of improvement for Datadog would be the documentation. While the tool is robust with many different capabilities, users would greatly benefit from more examples in the documentation. 

The number of current code snippets available in the docs is not enough, and some need to be updated even today. 

One function I would add would be a button to generate a report of the performance of a synthetic test and the performance of each of the steps in the test over time.

This timeline varies in terms of how long we've used the solution. We have one platform completely in the cloud and one still on-premises. We've had the solution for many years on AWS.

We use an enterprise version of a CMS platform which is enabling businesses to transmit content to their customers. The tool is fully customizable to the end user, including out-of-the-box integrations as well as APIs for custom plugin support. 

Our systems fully manage content using AWS as the back-end cloud provider. Assets are kept in secure buckets and utilize the Kubernetes infrastructure to deliver our product to end users and internal authors. Using the CMS allows for business people to manage content without needing development efforts.

This tool is the sole purpose of my company and the solutions we provide around it. Enabling customers to manage their content in a fast, reliable, and highly user-friendly setup has been critical to our success. 

Offering our product at SaaS, PaaS, cloud, and on-prem editions has enabled us to provide a solution for all types of customers. 

The platform appeals to companies spanning many industries on a global scale. 

Being based in SUI allows us to secure both the EU and other companies more easily.

The enterprise version of a CMS platform enables businesses to transmit content to their customers. 

The tool is fully customizable to the end user, including out-of-the-box integrations as well as APIs for custom plugin support. 

The content is fully managed within our systems using AWS as the back-end cloud provider. Assets are kept in secure buckets, and we can utilize the Kubernetes infrastructure to deliver our product to end users and internal authors. 

Using the CMS allows for business people to manage content without needing development efforts. Allowing this type of setup for business users has been a key reason for our success.

There is always room for improvement when dealing with cloud-based technologies. Mainly, I would say, it's just increasing our offerings to attract various other types of industries and businesses across more fields. 

New features as requested by our existing customers will help make the product better.

The product was self-developed.

We use a SaaS deployment. 

We use the solution primarily for platform monitoring for the services that are deployed in AWS. It gives a better way to monitor the services, including pods, cost, high availability, etc. This way, observability is ensured and also customer services are uninterrupted. 

Also, we host the data pipelines between the cloud and the on-prem for which Datadog is used to ensure better services. We report issues based on the metrics reported over it. 

Cost and performance optimization were the major enhancements for our organization. It gives us platform monitoring for the services that are deployed in AWS for a better way to monitor the services (pods, cost, high availability, etc.). With this product, we ensure that observability and also keep customer services uninterrupted. We host the data pipelines between the cloud and the on-prem. Datadog helps to ensure better services. We find we can report issues based on the metrics reported over it.

The observability pipelines are the most valuable aspect of the solution. 

Platform monitoring for the services that are deployed in AWS is helpful. It gives a better way to monitor the services. With Datadog, we ensure observability and maintain uninterrupted customer service. 

We can host the data pipelines between the cloud and the on-prem. Issues are easily reported.

The data streams are good. Data lineage is something that really helped in ensuring tracking of the data and metrics and also the volumes processed.

We'd like to see better transformers.

Live chat would be the best way to support us. 

Also, the features that we saw getting launched recently were something we expected and we're glad to see them coming.  

Geo-data is also something very critical that we hope to see in the future.

I've used the solution for two or more years. 

We primarily use the solution for log management and application performance monitoring. We have been getting into using more solutions on Datadog, such as runbooks, monitoring, and dashboards. 

Another area that we've been investing some time in is the database monitoring. We've been able to get some relatively new employees onboarded into the tool, and they've been able to create some meaningful dashboards and reports without too much hand-holding at all. 

We plan on exploring the synthetics solution as well.

We are still working through fully rolling the service out to our employees. Those that have so far begun using it have found that it decreases the time required to investigate and troubleshoot production issues. 

We have found that we're able to get in and out of troubleshooting issues much more rapidly, which in turn, of course, enables us to spend more time on our products. We are still investigating other areas where other Datadog services could potentially be injected into our workflows.

Correlation between logs and APM has been the most important feature that we've found in Datadog to date. Previous solutions around log collection or APM instrumentation were rather cumbersome to connect. We previously needed to use different solutions for each which were not connected and required complex queries and a lot of time investment by key employees.

The search and filtering capabilities are rather helpful as well. The aggregation of all currently available properties has been great. It's excellent that available options drop as filters are refined. This allows for a nuanced view of available data.

We intend on exploring other products at Datadog, so this list may expand.

I've found that the documentation is lacking in certain regards. In going through sessions around certain services, the presenter expressed opinions on best practices that are not covered by documented examples. 

In taking these thoughts to the "experts," further research is required both by us and those working the table to come to a solution that meets our needs. If there were more documentation on best practices this may be easier to manage.

I've been using the solution for ten years. 

The solution overall seems rather stable.

The solution seems scalable. We just need to keep an eye on the costs as it scales.

Customer support has been ok, yet not great. We've had ticket resolution drag on for weeks.

Neutral

We previously used Scalyr for logs and switched due to APM linkage.

The initial setup was straightforward.

We handled hte setup in-house.

We've saved many developer hours by using Datadog. We plan on expanding our investment in this solution (and thus our return).

Pricing can be a bit of a sell internally. We've found it to be worth it, though.

We came from using other solutions.

We are trying to get a handle on observability. Currently, the overall health of the stack is very anecdotal. Users are reporting issues, and Kubernetes pods are going down. We need to be more scientific and be able to catch problems early and fix them faster.

Given the fact that we are a new company, our user base is relatively small, yet growing very fast. We need to predict usage growth better and identify problem implementations that could cause a bottleneck. Our relatively small size has allowed us to be somewhat complacent with performance monitoring. However, we need to have that visibility.

We are still taking baby steps with Datadog. Hence, it's hard to come up with quantifiable information. The most immediate benefit is aggregating performance metrics together with log information. Having a better understanding of observability will help my team focus on the business problems they are trying solve and write code that is conducive to being monitored, instead of reinventing the wheel and relying on their own logic to produce metrics that are out of context

The most useful feature is the APM. Being able to quickly view which requests are time-consuming, and which calls have failed is invaluable. Being able to click on a UI and be pointed to the exact source of the problem is like magic. 

I'm also very intrigued by log management, although I haven't had quite a chance to use it very effectively. In particular, the trace and span IDs don't quite seem to work for me. However, I'm very keen on getting this to work. This will also help my developers to be more diligent and considerate when creating log data.

As a new customer, the Datadog user interface is a bit daunting. It gets easier once one has had a chance to get acquainted with it, yet at first, it is somewhat overwhelming. Maybe having a "lite" interface with basic features would make it easier to climb the learning curve.

Maybe the feature already exists. However, I'm not sure how to keep dashboard designs and synthetic tests in source control. For example, we may replace a UI feature, and rebuild a test accordingly in a pre-production environment, yet once the code is promoted to production, the updated test would also need to be promoted.

We have just started using the solution and have only used it for about two months.

We're new at this. That said, so far, there haven't been any issues to report.

I have not had the opportunity to evaluate the scalability.

Customer support is full of great folks! We're beginning our Datadog journey, so I haven't had that much experience. The little I have had has been great.

Positive

This is all new. 

We used to work with New Relic. New Relic has an amazing APM solution. However, it also became cost-prohibitive

Since we are relatively greenfield, it was relatively painless to set up the product. 

Our in-house DevOps team did the implementation.

I don't know what the ROI is at this stage.

I'm not sure what the exact pricing is. 

So far, it's been great!

The product is used for APM solutions for the metrics and traces for the REST API requests and service maps to understand the upstream and downstream services.

We are creating dashboards and widgets to monitor the status. We are creating alerts and monitors as well. We integrated the alerts and ticketing system in our organization with SNOW and Netcool.

We are using Kubernetes, AWS, and infrastructure metrics. We are using Kafka and Aurora Postgres logs as well, and we are using HTTP status codes to identify the error types.

So far, the solution works very well and solves most of the problems we have. Currently, we are trying to integrate the trace ID into Datadog and correlate the logs and metrics. However, Datadog is not supporting the spring-generated trace IDs, and they are not shown in the Datadog UI. It works in reverse. This means Datadog injects the DD-specific trace ID into the application logs, and those logs can be in other tools, for example, Cloud Watch and Splunk. 

The most valuable aspect is the APM which can monitor the metrics and latencies. There's a low error rate, and any alerts can be tagged to the service requests and sent via email to the required DLs. 

We can create incidents as well in our internal tools, like SNOW and Netcool.

The monitoring enables different dimensions of metrics to monitor the services and infrastructure. 

We have cloud infrastructure monitoring in Kubernetes nodes, pods containers, and ingress metrics.

Alerts are sent to an email in case of any issues. The metrics are used to create alerts.

The solution offers good dashboards, service maps, traces and flame graphs, HTTP status codes, power packs, service catalogs, and profiling.

While the logs module is not activated, we are using all other modules.

The correlation between the logs and the metrics needs improvement as most cases, we might use another logging tool (that is cheaper in cost) which then we have to link together. 

They can improve the SSO logging as well. Currently, we are logging in every two to three days by sending the login link explicitly.

I've been using the solution for two years. 

The stability is awesome. 

We are expanding beyond observability right now.

They offer pretty awesome customer support.

Positive

We did not previously use a different solution.

The initial setup was easy.

We implemented the solution with the help of a vendor team.

I'd rate the ROI ten out of ten.

I would recommend Datadog to others.

We also evaluated ECE and Splunk.

The solution has a great support model.