The technology itself is generally very useful and the interface it great.
Datadog Pro
DatadogExternal reviews
External reviews are not included in the AWS star rating for the product.
A product for everything
Datadog ASM has really helped protect our application in real time with the WAF
This stops security scans and other attacks right in their tracks.
Datadog an easy, visual way to monitor servers or containers
Great technology with a nice interface
What is most valuable?
What needs improvement?
There should be a clearer view of the expenses.
For how long have I used the solution?
I have used the solution for four years.
What do I think about the stability of the solution?
The solution is stable.
How are customer service and support?
I have not personally interacted with customer service. I am satisfied with tech support.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
I am using ThousandEyes and Datadog. Datadog supports AI-driven data analysis, with some AI elements to analyze, like data processing tools and so on. AI helps in Datadog primarily for resolving application issues.
How was the initial setup?
It was not difficult to set up for me. There was no problem.
What was our ROI?
I can confirm there is a return on investment.
What's my experience with pricing, setup cost, and licensing?
I find the setup cost to be too expensive. The setup cost for Datadog is more than $100. I am evaluating the usage of this solution, however, it is too expensive.
What other advice do I have?
I would rate this solution eight out of ten.
Makes it easy to track down a malfunctioning service, diagnose the problem, and push a fix
What is our primary use case?
We use Datadog for monitoring and observing all of our systems, which range in complexity from lightweight, user-facing serverless lambda functions with millions of daily calls to huge, monolithic internal applications that are essential to our core operations. The value we derive from Datadog stems from its ability to handle and parse a massive volume of incoming data from many different sources and tie it together into a single, informative view of reliability and performance across our architecture.
How has it helped my organization?
Adopting Datadog has been fantastic for our observability strategy. Where previously we were grepping through gigabytes of plaintext logs, now we're able to quickly sort, filter, and search millions of log entries with ease. When an issue arises, Datadog makes it easy to track down the malfunctioning service, diagnose the problem, and push a fix.
Consequently, our team efficiency has skyrocketed. No longer does it take hours to find the root cause of an issue across multiple services. Shortened debugging time, in turn, leads to more time for impactful, user-facing work.
What is most valuable?
Our services have many moving parts, all of which need to talk to each other. The Service Map makes visualizing this complex architecture - and locating problems - an absolute breeze. When I reflect on the ways we used to track down issues, I can't imagine how we ever managed before Datadog.
Additionally, our architecture is written in several languages, and one area where Datadog particularly shines is in providing first-class support for a
multitude of programming languages. We haven't found a case yet where we
needed to roll out our own solution for communicating with our instance.
What needs improvement?
A tool as powerful as Datadog is, understandably, going to have a bit of a learning curve, especially for new team members who are unfamiliar with the bevy of features it offers. Bringing new team members up to speed on its abilities can be challenging and sometimes requires too much hand-holding. The documentation is adequate, but team members coming into a project could benefit from more guided, interactive tutorials, ideally leveraging real-world data. This would give them the confidence to navigate the tool and make the most of all it offers.
For how long have I used the solution?
The company was using it before I arrived; I'm unsure of how long before.
Vendor Interactions Relation Management - DataDog
The complete visibility of the error traces makes it easy to track down any issues reported and thus making its fixes.
Very intuitive UI and powerfull integration
Deployment is super easy and quick with highly skilled support team. Datadog is one of the most frequenctly used tool in our organization and its been great. Documentation is very detailed and has improved over time allowing us to setup everything without major hurdles.
Monitoring Tool for Cloud Infra
Very useful Network Hosts
The user interface is intuitive, making it easy to manage domains, emails, and databases. The dashboard is well-organized, which is a plus for beginners who might feel overwhelmed by technical details.
Good RUM and APM with good observability
What is our primary use case?
We use Datadog across the enterprise for observability of infrastructure, APM, RUM, SLO management, alert management and monitoring, and other features. We're also planning on using the upcoming cloud cost management features and product analytics.
For infrastructure, we integrate with our Kube systems to show all hosts and their data.
For APM, we use it with all of our API and worker services, as well as cronjobs and other Kube deployments.
We use serverless to monitor our Cloud Functions.
We use RUM for all of our user interfaces, including web and mobile.
How has it helped my organization?
It's given us the observability we need to see what's happening in our systems, end to end. We get full stack visibility from APM and RUM, through to logging and infrastructure/host visibility. It's also becoming the basis of our incident management process in conjunction with PagerDuty.
APM is probably the most prominent place where it has helped us. APM gives us detailed data on service performance, including latency and request count. This drives all of the work that we do on SLOs and SLAs.
RUM is also prominent and is becoming the basis of our product team's vision of how our software is actually used.
What is most valuable?
APM is a fundamental part of our service management, both for viewing problems and improving latency and uptime. The latency views drive our SLOs and help us identify problems.
We also use APM and metrics to view the status of our Pub/Sub topics and queues, especially when dealing with undelivered messages.
RUM has been critical in identifying what our users are actually doing, and we'll be using the new product analytics tools to research and drive new feature development.
All of this feeds into the PagerDuty integration, which we use to drive our incident management process.
What needs improvement?
Sometimes thesolution changes features so quickly that the UI keeps moving around. The cost is pretty high. Outside of that, we've been relatively happy.
The APM service catalog is evolving fast. That said, it is redundant with our other tools and doesn't allow us to manage software maturity. However, we do link it with our other tools using the APIs, so that's helpful.
Product analytics is relatively new and based on RUM, so it will be interesting to see how it evolves.
Sometimes some of the graphs take a while to load, based on the window of data.
Some stock dashboards don't allow customization. You need to clone them first, but this can lead to an abundance of dashboards. Also, there are some things that stock dashboards do that can't yet be duplicated with custom dashboards, especially around widget organization.
The "top users" widget on the product analytics page only groups by user email, which is unfortunate, since user ID is the field we use to identify our users.
For how long have I used the solution?
I've used the solution for three and a half years.
What do I think about the stability of the solution?
The solution is pretty stable.
What do I think about the scalability of the solution?
The solution is very scalable.
How are customer service and support?
Support was excellent during the sales process, with a huge dropoff after we purchased the product. It has only recently (within the past year) they have begun to reach acceptable levels again.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We did not have a global solution. Some teams were using New Relic.
How was the initial setup?
The instructions aren't always clear, especially when dealing with multiple products across multiple languages. The tracer works very differently from one language to another.
What about the implementation team?
We handled the setup in-house.
What's my experience with pricing, setup cost, and licensing?
We have built our own set of installation instructions for our teams, to ensure consistent tagging and APM setup.
Which other solutions did I evaluate?
We did look at Dynatrace.
What other advice do I have?
The service was great during the initial testing phase. However, once we bought the product, the quality of service dropped significantly. However, in the past year or so, it has improved and is now approaching the level we'd expect based on the cost.