Datadog Reviews

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.

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.

We are using the solution for migrating out of the data center. Old apps need to be re-architected. We plan to move to multi-cloud for disaster recovery and avoid vendor lockouts. The migration is a mix between an MSP (Infosys) and in-house devs. The hard part is ensuring these apps run the same in the cloud as they do on-prem. Then we also need to ensure that we improve performance when possible. With deadlines approaching quickly, it is important not to cut corners which is why we needed observability.

The product has created a paradigm shift in how we deploy monitoring. Before, we had a one-to-one lookup in service now. This wouldn't scale, as teams wouldn't be able to create monitors on the fly and would have to wait on us to contact the ServiceNow team to create a custom lookup. Now, in real-time, as new instances are spun up and down, they are still guaranteed to be covered by monitoring. This used to require a change request, and now it is automatic.

For use, the most valuable features we have are infrastructure and APM metrics. The seamless integration between Datadog and hundreds of apps makes onboarding new products and teams a breeze. 

We rely heavily on the API crawlers that Datadog uses for cloud integrations. These allow us to pick up and leverage the tags teams have already deployed without having also to make them add them at the agent level. Then we use Datadogs conditionals in the monitor to dynamically alert hundreds of teams, and with the ServiceNow integration, we can also assign tickets based on the environment. Now, our top teams are using APM/profiler to find bottlenecks and improve the speed of our apps.

The real issue with this product is cost control. For example, when logs first came out, they didn't have any index cuts. This leads to runaway logs and exploding costs. 

It seems that admin cost control granularity is an afterthought. For example, synthetics have been out for over four years, yet there are no ways to limit teams from creating tests that fire off every minute. If we could say you can't test more than once every five minutes that would save us 5X on our bill.

I've been using the solution for about three years. 

The solution is very stable. There are not too many outages, and they fix them fast.

It is easy to scale. It's why we adopted it. 

Before premium support, I would avoid using them since it was so bad.

Neutral

We previously used App Dynamics. It isn't built for the cloud and is hard to deploy at scale.

The initial setup was not complex. We just had to teach teams the concept of tags.

We implemented the solution in-house. It was me. I am the SME for Datadog at the company.

We have seen an ROI. It has saved months of time and reduced blindspots for all app teams.

We'd advise new users to be careful with logs, and the APM as those are the ones that can get expensive fast.

We looked into Dynatrace. However, we found the cost to be high.

We share dashboards, set up alerts, and monitor everything that happens in our system. We use it in staging, features, production, and our load test environment. It is exceptionally helpful for making our engineering more data-driven. 

I came from a company that believes we should focus on being telemetry driven. Instilling this in a smaller, less mature engineering organization has been challenging. However, it is much easier while using Datadog.

The dashboards are great. They are an easy way to give visibility into what we need to watch with others who are not SMEs.

I enjoy the custom metrics. With this, we can take things that were once logs and then retain them longer.

We are able to parse logs. To be honest, this was only useful due to the fact that we had not yet set up the Datadog agent properly in PHP. Once we did this, the Datadog log parsing was no longer needed.

The ability to pin to a date and time is very helpful. This allows us to pinpoint exactly what was happening.

We need more advanced querying against logs. While most issues I have had here can be alleviated by way of sending better-formatted logs, it would be cool to do SQL-type queries against our data.

We need a way to see dashboard metadata. We launched a huge customer, and we saw more people using Datadog than ever across the entire organization, yet had no way to tell.

It would be ideal if we had some way to compare arbitrary date times more easily. We would love to use the Diff Graph command against some hard-coded value, for instance, against some known event.

I've used the solution for eight months.

The scalability is great!

We previously used New Relic. I was not part of the decision-making team that made the switch.

The ROI is the speed at which we can debug live sites. It has been excellent. It's amazing how many incidents we can capture before customers notice.

We looked into New Relic and a home-brewed solution as potential other options.

We primarily use the solution for log monitoring across our entire cloud infra (EB, EC2, Batch, and Lambda).

This is in addition to Rstudio Workbench, which has its own logs that would not be picked up via Cloudwatch(https://docs.rstudio.com/ide/server-pro/server_management/logging.html#default-log-file-locations). 

We own several dozen of these servers, and we used to manage instance logs by tailing logs when incidents occurred. Datadog allows for much better visibility across our entire fleet and has saved us countless hours.

It is now way easier to search in one place rather than across all of Cloudwatch (and needing to know log groups, etc.). 

Primarily, we run several separate deployments of Rstudio Workbench, which has its own logs that would not be picked up via Cloudwatch. 

We own several dozen of these servers. We used to manage instance logs manually. 

Datadog allows for much better visibility.

We've found it most useful for managing Rstudio Workbench, which has its own logs that would not be picked up via Cloudwatch. 

Datadog allows for much better visibility across our entire fleet and has saved us countless eng hours as a result. 

We plan on trying out offerings such as APM moving forward too.

Some things that Datadog does very well:

• Technical documentation (the docs are clear, concise, and include realistic code samples)
• Overall education efforts (e.g. the codelabs/workshops)

We primarily use the log management functionality, and the only feedback I have there is better fuzzy text searching in logs (the kind that Kibana has). 

I've learned about a ton of other offerings, like APM, NPM, etc., over the course of workshops. Once I try those out, I'm sure I will have additional feedback.

I've used the solution for one year.