Datadog Reviews

We primarily use Datadog for alerts. If we're running out of database connections or CPU credits we want to find out in Slack. Datadog provides nice features for that.

Secondarily, we use Datadog for analyzing historical trends and forecasting potential issues.

I'm trying to learn how to add in Continuous Profiler in our primary backend servers and set up Synthetic Tests for monitoring our front end.

Everything is mostly on AWS, and the Datadog integrations help a ton.

Datadog has helped us a ton by allowing us to set up a multitude of easily configurable alarms across our tech stack and infrastructure. It doesn't matter if it's in AWS Lambda or a Docker container in AWS EC2, Datadog's intuitive interface makes alarms incredibly easy to configure, reducing our resolution time for incidents.

A lot of the value comes from how frictionless the integrations are. Adding in a Datadog agent or flipping a switch on the Datadog UI to start streaming Lambda data makes the product so incredibly appealing for my company.

The monitoring feature has been the most valuable.

I really like the dashboard. Monitoring has a straightforward tie-in to business value at my company (i.e. declaring incidents, etc). Things like having a dashboard and APM make my job easier. That said DevX is a little bit of a harder sell to executives in my company.

The dashboard feature makes it so easy to inspect multiple metrics at once across services. It's truly been a lifesaver when I'm personally trying to understand why performance degradation is happening.

I found the documentation can sometimes be confusing. I tried configuring APM for some of our Python containers, and I had to cross-reference multiple blog posts and the official documentation to figure out which Datadog-agent to use. If I needed a ddtrace trace, what environment variables I should set, etc. 

Furthermore, to generate my own traces, I wasn't aware that ddtrace adds its own "monkey patching," which led to headaches with respect to configuring the service for RabbitMQ.

A more unified and up-to-date documentation suite would be greatly appreciated.

I've used the solution for about two years.

I don't recall seeing an incident from Datadog in the past couple of years and that's been wonderful.

The solution is incredibly scalable! To be fair, our data throughput to Datadog isn't super huge, however, we have never seen issues as it scaled to handle more of our data.

We used to use AWS Cloudwatch for a lot of our monitoring needs. That said, the interface felt clunky, confusing, and limited.

We don't have hard numbers on ROI. That said, overall, it has been a wonderful addition to our tooling suite.

We also looked at Honeycomb and are currently using both in production.

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 use Datadog for observability and system/application health, mainly for product support, triaging, debugging, and incident responses.

We use a lot of the logging and the Datadog agent to collect logs, metrics, and traces from our GKE workloads. We use APM and continuous profiling for latency and performance measurement. We use RUM to observe frontend user events, such as tracing on request and what actions they take before errors occur. We also use error tracking and source maps to debug production failures.

We are still relatively new to the product, and we are planning to use more of the notebook functionality and power packs to record run books and break knowledge silos. We also need to utilize dashboards and continuous profiling more for performance measurement and integrate Datadog alerts for incident response.

We have way more observability than what we had before - on the application and the overall system. That includes the GKE cluster, nodes, and pods. It's helped with our cloud-run instances, databases, and data storage.

We also started observability in the CI pipeline to measure our CI performance, as it was a pain point for us. We are aiming to do incremental deployments and releases, and the bottleneck so far has been our CI performance. The visibility on which actions or functions take the most time allows us to pinpoint and focus on improving configurations on these.

We use structure logging a lot to triage production issues. The querying, attributes and tags manipulation, and customization have been very helpful in isolating and filtering environments. The integration with Winston logger has also been a breeze.

First and foremost, was that structured logging, tags, and attributes have not only allowed us to narrow down to a problem quickly in production, they have also let us create dashboards from these logs to understand more user behaviors, such as how many users stop and leave our application before an upload has completed. That helps us understand how important processing time is to a user.

We also intend to use distributed tracing more to understand where the error has occurred in a particular request.

Definitely, documentation could use improvement. As I navigated and try to find instrumentation and implementation details, I discovered inconsistency among SDKs based on languages. 

There are also places where highlighting can be improved. I once created an issue on GitHub, and it was resolved right away by an engineer. He pointed out that it was actually in the documentation. I looked again and found it was not very obvious. We were stuck on the problem for days.

Auto instrumentation on tracing has not been very easy to find in the documentation. We ended up using OpenTelemetry, yet the conversion between tracing contexts has been difficult.

We've used the solution between six months and a year. 

Customer service and support are generally very fast. I did experience one ticket, which involved changing the log index retention period, not being responded to. Any support tickets related to technical issues were resolved pretty fast.

Positive

We used to use GCP Stackdriver for logging and monitoring since our infrastructure is all GCP based. It was lacking a lot, particularly on tracing and structured logging. We often had a lot of trouble triaging and diagnosing a production problem. Datadog's specialty is observability. Since we started using the product, we were able to create dashboards, and utilize APM, continuous profiling, RUM, and distributed tracing for production support and user trends.

Datadog also offers labs and workshops for its products, which is very helpful.

We implemented the product ourselves.

I'm not sure what our ROI would be.

We started with on-demand pricing as we were re-writing our product, and we weren't sure about the total usage. After we went into production and released the product, we experienced a price surge. Fortunately, our Datadog account manager reached out to us and suggested a monthly subscription, which is what we'll be switching to.

I'd advise keeping an eye on the usage and possibly setting up some monitoring on price. We didn't have much of a setup cost; we started with a free trial and continued with on-demand after the trial ended.

We didn't evaluate many of the other options. However, we do also use OpenTelemetry, which is vendor agnostic and integrates with Datadog.

We always keep the Datadog agent to the latest version.

We primarily use Datadog for logs, APM, infrastructure monitoring, and lambda visibility.

We have built a number of critical dashboards that we display within our office for engineers to have a good understanding of the application performance, as well as business partners to understand at a high level the traffic flowing through the app.

We started with logging, as our primary monitor, and have shifted to APM to get a deeper understanding of what our system is doing, and how the changes we are making impact the apps.

Datadog has given us near-live visibility across our entire cloud platform. We are finally in a state where we are alerting our users about degraded performance well before the helpdesk tickets start rolling in.

We are making major architectural decisions based on the data we are getting from Datadog. It also gives us an idea of where the complexity really lies in some older, monolithic apps. 

We have used the APM endpoint monitoring to prioritize work on slower endpoints because we can see the total count, as well as the latency. That has been a big driver in our refactor work prioritization.

We have struggled to get more business-centric measures in our code to surface actual business values in our reports, but that is our next initiative.

We started with Log analytics in the beginning stages of our monitoring journey. Those were very insightful, but obviously only as useful as we made them with good logging practices.

The dashboards we created are core indicators of the health of our system, and it is one of the most reliable sources we have turned to, especially as we have seen APM metrics impacted several times lately. We can usually rely on logs to tell us what the apps are doing.

APM and Traces have been crucial to understanding how users are actually using the app. That drives a lot of our decisions around refactoring and focusing our limited engineering resources.

Continued improvement around cost and pricing model is needed. It is pretty complex and takes a fair amount of intimate knowledge to know exactly how turning on a single function is going to impact your bill, especially when you don't see the metrics for a day or two. 

We have recently had a number of issues with stability and delays on logging, monitoring, metric evaluation, and alerts. More often than not in the past month, it seems that we get the banner across the to of our dashboards that some service is impacted. They don't always show up on the incident page, either.

We have been using Datadog for two years.

Overall, it has been fairly stable for us. There are the occasional issues with importing data, that has usually been resolved in a short time. We have never had an issue where that data was lost, just delayed, and eventually backfilled. 

It seems (anecdotally, of course) that there have been a few more stability issues lately. We have noticed several days that we are getting in-app alert banners indicating that some metric or log ingestion was delayed, or the web app itself was experiencing severe slowness. 

Overall, these issues are resolved rather quickly - kudos to their engineering teams. I hear that they actually use Datadog to monitor Datadog. 

Datadog is very scalable but just watch the cost.

Technical support is hit and miss; there are a number of nuances to how this tool should be implemented, and it is difficult to re-explain how our infrastructure and applications are set up every time we need an in-depth investigation to understand what is broken.

Previously, we used AppDynamics. The pricing model didn't seem to fit with actual cloud spend. Now we may have swung the pendulum a little too far, and seem to be dealing with pricing on every facet of the application. 

The initial setup was pretty straightforward. Additional tweaks and configuration have been a bit more difficult as we get deeper and deeper into the guts of the integrations. Making sure we are keeping up with a rapid release schedule, and keeping our server clients in sync with our app packages has been troublesome. There have been some major changes in the APM that have introduced a number of bugs and broken some of our dashboards and alerts.

Our in-house team handled the deployment, with a lot of tickets created for the Datadog team.

ROI is difficult to measure completely. Our first year spend compared to our second and now going into the third year spend have been significantly different.

My advice is to really keep an eye on your overage costs, as they can spiral really fast. We turned on some additional span measures and didn't realize until it was too late that it had generated a ton.

Frankly, we love the visibility it gives us into our applications, but it is a bit cumbersome to ensure we are paying for the right stuff. Overall, the cost is worth it, as it helps us keep system-critical applications up and running, and reduces our detection and correction times significantly.

We evaluated Dynatrace and AppD before choosing this product.

Datadog requires pretty close supervision on the usage page to ensure you aren't going out of control. They have provided a bunch of new features to assist in retention percentage, but it can be a bit confusing on what is being retained, and what can be viewed again after triggering an alert. It's a difficult balance of making sure you are getting the right data for alerts, and still having the correct information still available for research after the fact.

We were in need of a cloud monitoring tool that was operationally focused on the AWS Platform. We wanted to be able to responsibly and effectively monitor, troubleshoot, and operate the AWS platform, including Server, Network, and key AWS Services.

Tooling that highlighted and detected problems, anomalies, and provided best practice recommendations. Tooling that expedites root-cause analysis and performance troubleshooting.

Datadog provided us the ability to monitor our cloud infrastructure (network, servers, storage), platform/middleware (database, web/applications servers, business process automation), and business applications across our cloud providers.

Datadog provided us the tooling to help us effectively monitor, troubleshoot, and operate the AWS platform, including Server, Network, Database, and key AWS Services. It highlights detected problems and anomalies and provides best practice recommendations, expedites root-cause analysis, and performance troubleshooting.

Datadog provides analytics and insights that are actionable through out-of-the-box visualizations, dashboards, aggregation, and intuitive searching that shortens the time to value and account for our limited time & resources we have to operate in production.

The most valuable feature is the dashboards that are provided out of the box, as well as ones we were able to configure. Specific Dashboards that were provided that made things easier were EC2, RDS, Kubernetes dashboards.

We also use the logging tool, which makes searching for specific error logs easier to do.

Datadog Logging provides the capability for us to use AWS logs such as VPC Flow Logs, ELB, EC2, RDS, and other logs that provide lots of relevant operational data but are not actionable. Datadog provides a tool that can provide us analytics and insights that are actionable for visualizations, dashboards, alerting, and intuitive searching.

More pre-configured "Monitor Alerts" would be helpful. Datadog's knowledge of its customers and what they are looking for in terms of monitoring and alerting could be taken advantage of with pre-canned alerts. They have started this with "Recommended Monitors".  That feature was very helpful when configuring our Kubernetes alerts. More would be even better. 

Datadog tech support is very good. One area that could be more helpful is actually talking to someone or sharing your screen to help troubleshoot issues that arise. For new cloud engineers just coming into the cloud monitoring field, there is a learning curve. There is a lot to learn and figure out. For example, we still ran into some issues configuring the private link and more videos of how to do things could be of use.

We have been using Datadog for one year.

We have not run into any issues with stability.

The scalability of Datadog is very good.

Customer service has been excellent.  I communicate weekly a Datadog Customer Success Manager.  He helps me followup on any open issues or questions that we may have.  Technical support has been very good. Opening tickets is easy.  Sometimes a Tech Engineer may take a bit of time to get back with you.  Communicating with Tech Engineer has to be done via ticket/email - no phone assistance is available.

we did not.

Procedures for setup seemed straightforward but once you got going, there were some issues. For us, getting our private link to work needed additional tech support. They were able to help us resolve the issue we were experiencing. I think the procedures could be done a bit better to help you with setup.

We deployed it ourselves.

Datadog helps us minimize downtime and helps us resolve issues quickly.  

Pricing seemed easy until the bill came in and some things were not accounted for. The issue may have been that we didn't realize what was being accounted for, such as the number of servers and the number of logs being ingested.

Datadog had really good pre-sale reps that work with us but need to make sure all the details are covered.

The solution we were looking for needed to provide out-of-the-box capabilities that shorten the time to value. We had limited time & limited resources. Datadog had high recommendations in these areas, so we decided to do a trial with them.

We are very pleased with Datadog overall.

Datadog has assigned an account rep to us that meets with us regularly to make sure all our needs are being met and help us get answers to any questions or issues we are running up against. They have been of great helping us standup monitoring of our Kubernetes environment.

Datadog is expensive. 

The tool's deployment is easy. 

The solution's pricing depends on project volume. 

I rate Datadog a seven out of ten. 

Our use case is to provide cloud organization application monitoring. I use it for insight into what host in what region has activity or what market is using Datadog to its fullest potential and utilizing that for cost. This may also help determine who is using monitoring and setting alerts or just setting up monitoring and not doing anything about it. The use case can also be to check when the host or applications are down, or if the usage of CPU, memory, etc, is too high.

The solution has improved our organization from a market perspective. We have multiple departments and need some time to gather that data from a grouping point of view. Grouping that data via tag or seeing the separation is easy. In addition, it provides metrics and insights for senior leadership to have a high level of usage and cost. Application teams have better insight into their application, outages, when to plan for patches, updates, etc. Also, they have a better understanding of where the data gaps may be.

The infrastructure is the most valuable. It has a high-level insight into the infrastructure model of the application and provides important detailed data on the host and metrics, which is the main concern of our customers. It provides confirmation that the layer where the application is running is monitored and will be alerted when it is down and not functional. The customers can have ease of mind knowing their metrics are accurately being measured. The value of data provided, including service name, logs, and all other pertinent details tied to the host, makes it a valuable source of data

The solution can be improved via open communication to the broader audience on what has changed and what has not changed. I sometimes log in and see items changed, either in the UI or a feature enabled. To see it for the first time without proper communication can sometimes come as a shock.

I have been using the solution for three years.

The stability is great.

Technical support is great. Datadog has the resources and knowledge to tackle questions.

Positive

I did not previously use a different solution.

The initial setup is straightforward.

The initial setup was handled in-house.

I did not evaluate any other solutions.

We use the solution for application hosting and a little bit of everything when it comes to supporting a worldwide logistics tracking service. It's used as a central service for collecting telemetrics and logs. We find it does the same work as all of our old tools combined, including Prometheus, Kibana, Google Logs, and more; putting all of this information in a single platform makes it easy to corroborate information and associate a request with the data, which might be lost when it is saved as logs.

At my organization, we have plenty of microservices written in different languages. Different teams prefer one or the other framework or library within those languages.

With Datadog, we can get in a single line and march in the same direction; our logs and metrics are collected in the same fashion, making it easy to find bugs or integration problems across services and understand how they interact with other systems.

I primarily prefer to utilize the profiling and tracing feature. It can potentially be used as a more-informed alternative to logs.

Beyond that, anything I've wanted to do, I found a way to get it done through Datadog. It allows for testing, logging, hardware monitoring, system performance, memory consumption, advanced observability, AI assistance, cross-team collaboration, and business analytics. Datadog helps some of the world’s biggest brands transform faster with the help of true AIOps, AI-assisted answers, UX and business analytics, cloud observability, and smart AI assistance.

It's all supporting my desire to build a great application, and in a centralized SaaS application, it's hard to say anything can beat it.

The storage of logs is a little bit unexpected; most services generate gigabytes of logs, and their size is not excessive. When it comes to storing the logs with Datadog, I'm not sure why it costs so much to store gigabytes or terabytes of information when it's a fraction of the cost to do so myself.

I've used the solution for one year.

We have no concerns with stability.

It appears to be that there are no issues with scaling.

Technical support is slow. It takes forever to get responses from the support team.

Neutral

I've previously used Kibana and Prometheus. We are still using these.

Setting up through the environment variables made it unbelievably easy to get started.

We've implemented the solution in-house.

I do not have this number off-hand, as I am not the finance guy. I just like the product.

I'd advise new users not to start off by sending logs.

We did not really look at other options.