Our main use case for Datadog includes monitoring and logs, custom metrics, as well as utilizing the APM feature and synthetic tests in our day-to-day operations.

A quick specific example of how Datadog helps with our monitoring and logs comes from all our applications sending logs into Datadog for troubleshooting purposes, with alerts built on top of the logs, and for custom metrics, we send our metrics from the applications via Prometheus to Datadog, building alerts on top of those as well, sometimes sending critical alerts directly to PagerDuty.

We generally have monitors and alerts set up for our applications and specifically rely on them to check our critical business units, such as databases; in GCP, we use Cloud SQL, in AWS, we use RDS, and we also monitor Scylla databases and EC2 instances running Kafka services, which we heavily depend upon. Recently, we migrated from US one to US five, which was a significant shift, requiring us to migrate all alerts and monitors to US five and validate their functionality in the new site.

The best feature Datadog offers is its user-intuitive interface, making it very easy to track logs and custom metrics. We also appreciate the APM feature, which has helped reduce our log volumes and custom metric volumes, allowing us to turn off some custom metrics.

We recently learned how tags contribute to custom metrics volume, which led us to exclude certain tags to further reduce that volume, and we implement log indexing and exclusion filters, leaving us with much to explore and optimize in our use of Datadog as our major observability platform.

Regarding metrics showing our improvements, the MTTR has been reduced by about 40% after integrating Datadog with PagerDuty, and we've seen our costs significantly drop in the most recent renewal after three years' contract.

Operationally, we spend about 30-40% less time correlating logs and metrics across services, while potential areas for improvement in Datadog include its integration depth and providing more flexible pricing models for large metric and log volumes.

I would suggest having an external Slack channel for urgent requests, which would enable quicker access to support or a dedicated support team for our needs.

I choose eight because, while we have used Datadog for three years and experienced growth in our business and services, the cost has also increased with the growth in metrics and log volumes, and proactive cost management feedback has not been provided to help manage or budget those rising costs. Thus, I'd like to see more proactive cost management in the future, as the pricing model seems to escalate quickly with increasing metrics ingestion and monitoring across clouds. Datadog is a powerful and reliable observability platform, but there is still room for improvement in cost efficiency and usability at scale.

Regarding pricing, setup costs, and licensing, I find Datadog's pricing model transparent but scaling quickly; the base licensing for host integration is straightforward, but costs can rapidly climb as we add custom metrics and log ingestion, especially in dynamic Kubernetes or multi-cloud environments, with the pricing being moderate to high, and while cost visibility is straightforward, it could become challenging with growing workloads. The upfront setup cost is minimal, mainly involving fine-tuning dashboards, tags, and alerts, making licensing very flexible to enable features as needed.

I have been working in my current field for roughly around 10 years, starting my AWS journey about 10 years ago, mainly focused on infrastructure and observability.

I believe Datadog is stable.

Datadog's scalability is impressive, as it has the necessary integrations, supports agent-based and cloud-native solutions, and accommodates multi-cloud, multi-region features, making overall performance very good.

Customer support has improved recently with online support available through a portal, allowing for quicker access to help.

Neutral

Previously, we used Splunk SignalFx for a couple of years, switching to Datadog because of Datadog's user-intuitive interface, which was lacking in SignalFx at the time.

Datadog has had a significant positive impact on our organization overall, particularly in visibility, reliability, and cost efficiency, allowing us to centralize metrics, logs, and traces across our cloud, moving from reactive to proactive monitoring, with improvements including faster incident detection and resolution, enhanced service reliability, better cost and resource optimization, and shared dashboards providing the engineering and product teams a single source of truth for system health and performance, thus enhancing our overall observability and operational efficiency.

I believe Datadog has delivered more than its value through reduced downtime, faster recovery, and infrastructure optimization; although we sometimes miss critical alerts, overall, it has improved our team's efficiency by maybe 30% less time spent troubleshooting logs and custom metrics while providing measurable ROI through enhanced system reliability, reduced incident costs, and infrastructure spending optimization.

We only evaluated SignalFx before choosing Datadog, as Datadog offered simpler scaling, better management, broader integrations, and dashboards, allowing for easier monitoring of our multi-cloud setup.

After reducing log and custom metric volumes, we notice a significant reduction in costs without any performance issues on our end, actually seeing a lot of cost reductions.

I strongly recommend using Datadog, but suggest being proactive about resource usage and tracking anomalies monthly.

I find the interview process okay, although it runs longer than I expected, exceeding the anticipated 10 minutes.

My rating for Datadog is 8 out of 10.

My team and I primarily rely on Datadog for logs to our application to identify issues in our cloud-based solution, so we can take the requests and information that's being presented as errors from our customers and use it to identify what the errors are within our back-end systems, allowing us to submit code fixes or configuration changes.

I had an error when I was trying to submit an API request this morning that just said unspecified error in the web interface. I took the request ID and filtered a facet of our logs to include that request ID, and it gave me the specific examples, allowing me to look at the code stack that we had logged to identify what specifically it was failing to convert in order to upload that data.

My team doesn't utilize Datadog logs very often, but we do have quite a few collections of dashboards and widgets that tell us the health of the various API requests that come through our application to identify any known issues with some of our product integrations. It's useful information, but it's not necessarily stuff that our team monitors directly as we're more of a reactionary team.

The best features Datadog offers, in my experience, are the ability to filter down by facets very quickly to identify the problems we're experiencing with our individual customers using our cloud application. I really enjoy the trace option so that I can see all of the various components and how they communicate with each other to see where the failures are occurring.

The trace option helps us spot issues by giving access to see if the problem is occurring within our Java components or if it's a result of the SQL queries, allowing us to look at the SQL queries themselves to identify what information it's trying to pull. We can also look at other integrations, whether that's serverless Lambda functions or different components from our outreach.

Datadog has impacted our organization positively because the general feeling is that it's superior to the ELK stack that we used to use, being significantly faster in searching and filtering the information down, as well as providing links to our search criteria that our development teams and cloud operations teams can use to look at the same problems without having to set up their own search and filter criteria.

For the most part, the issues that we come across with Datadog are related to training for our organization. Our development and operations teams have done a really good job of getting our software components into Datadog, allowing us to identify them. However, we do have reduced logging in our Datadog environment due to the amount of information that's going through.

The hardest thing we experience is just training people on what to search for when identifying a problem in Datadog, and having some additional training that might be easily accessible would probably be a benefit.

At this point, I do not know what I don't know, so while there may be options for improvements, Datadog works very well for the things that we currently use it for. Additionally, the extra training that would be more easily accessible would be extremely helpful, perhaps something within the user interface itself that could guide us on useful information or how to tie different components or build a good dashboard.

I have worked for Calabrio for 13 years.

Datadog is very stable.

Datadog's scalability is strong; we've continued to significantly grow our software, and there are processes in place to ensure that as new servers, realms, and environments are introduced, we're able to include them all in Datadog without noticing any performance issues. The reporting and search functionality remain just as good as when we had a much smaller implementation.

Previously, we used the ELK stack—Elasticsearch, Logstash, and Kibana—to capture data. Our cloud operations team set that up because they were familiar with it from previous experiences. We stopped using it because as our environment continued to grow, the response times and the amount of data being kept reached a point where we couldn't effectively utilize it, and it lacked the capability to help us proactively identify issues.

A general impression is that Datadog saves time because the ability to search, even over the vast amount of AWS realms and time spans that we have, is significantly faster compared to other solutions that I've used that have served similar purposes.

I would advise others looking into using Datadog to identify various components within their organization that could benefit from pulling that information in and how to effectively parse and process all of it before getting involved in a task, so they know what to look for. Specifically, when searching for data, if a metric can be pulled out into an individual facet and used, the amount of filtering that can be done is significantly improved compared to a general text search.

I would love to figure out how to use Datadog more effectively in the organization work that I do, but that is a discussion I need to have with our operations and research and development teams to determine if it can benefit the customer or the specific implementation software that I work with.

On a scale of one to ten, I rate Datadog a ten out of ten.

My main use case for Datadog is for security SIEM, log management, and log archiving.

In my daily work, we send all our logs from different cloud services and SaaS products, including Okta, GCP, AWS, GitHub, as well as virtual machines, containers, and Kubernetes clusters. We send all this data to Datadog, and we have numerous different monitors configured. This allows us to create different security features, such as security monitoring and escalate items to a security team on call to create incident response. Archiving is significant because we can always restore logs from the archive and go back in time to see what happened on that exact day. It is very helpful for us to investigate security incidents and infrastructure incidents as well.

Regarding our main use case, we use the Terraform provider for Datadog, which is probably one of the biggest benefits of using Datadog over any other similar tool because Datadog has great Terraform support. We can create all our security monitoring infrastructure using Terraform. Even if something goes wrong and the Datadog tenant becomes completely compromised or if all our monitors were to get erased for whatever reason, we can always restore all our monitoring setup through Terraform, which provides peace of mind.

The best features Datadog offers are not necessarily about having the best individual features, but rather the sheer quantity of different features they offer. I appreciate how you can reuse a query across different indexes for logs or security monitoring. The syntax remains consistent for everything, so you do not have to learn multiple languages. Similarly, for different types of monitors, you can always reuse the same templating language, which makes things much more efficient.

Datadog positively impacted our organization by making us more cautious about how we manage our logs. Before Datadog, we would ingest substantial amounts of data without considering indexing priorities. We became more strategic about what we index, particularly for security and cloud audit logs. We improved our approach to indexing retention and determining which types of logs are important. Overall, we enhanced our internal log management practices.

After implementing Datadog, we observed specific improvements in outcomes and metrics. We started analyzing our logs more thoroughly than before, identifying different patterns, and determining log importance levels. We began looking for more signals from audit logs and distinguishing between critical and non-critical information. The most significant metric improvement has been reduced incident investigation time.

Datadog can be improved by addressing billing and spend calculation methods, as it would be better if these were more straightforward. Currently, these calculations can be complex. Additionally, while we use Terraform extensively, not everything is available in Terraform. It would be beneficial to have more features supported in Terraform, particularly some security features that have been available for a while but still lack Terraform support.

I have been using Datadog for about four years.

Datadog is very stable.

Datadog's scalability is excellent. We have never encountered any issues.

The customer support is good. I have never had any issues.

I would rate the customer support as nine out of ten.

Positive

We previously used New Relic and switched because it was not very effective.

My experience with pricing, setup cost, and licensing indicates that it was somewhat expensive.

I have seen a return on investment with Datadog, particularly in time saved responding to incidents. Regarding staffing requirements, that metric isn't applicable for our use case since log management and security monitoring inherently require personnel to respond. However, it has definitely improved our efficiency in terms of response time, though this isn't a hard metric but rather based on experience.

I do not remember evaluating other options before choosing Datadog as it was a long time ago.

I would rate Datadog an eight out of ten because while it is expensive, it offers numerous features, though sometimes it attempts to do too much.

My advice to others considering Datadog is to explore other products and calculate potential spending carefully. If Terraform support is important to your organization, then Datadog is an excellent choice. However, keep in mind that costs will increase significantly as you scale, and different features have varying pricing structures.

Overall rating: 8/10

My main use case for Datadog is application monitoring.

Specifically for application monitoring, we monitor our production Laravel instances using APM spans and tracing.

In addition to application monitoring, I also use Datadog to monitor our log management for our applications that are both on-prem and in the cloud, as using the AWS integration.

In my experience, the best features that Datadog offers us include unprecedented visibility and the ability to dive deep on application debugging.

Datadog's visibility and debugging features help me day-to-day; specifically, we had an application that was throwing a bunch of errors causing an issue in our production database. Using Datadog, we were able to immediately isolate the error and plan around it.

Datadog has positively impacted my organization. I think it has given us not only the specific debug and error codes that we're looking for, but it has changed the entire company's mindset in how to extract value from data that's been lying around in our internal systems for years now and given everybody a new perspective on monitoring and debugging.

Since adopting Datadog, I've noticed specific outcomes. We've begun to handle our log management internally in a more efficient manner, so we've actually reduced our disk space as simplified our backup procedures and process chains using Datadog. Now that we have extracted the value from the logs and the traces and the debug logs, we no longer have to rely so much on traditional text-based logs or even digging into the code and the error files themselves.

The only improvement I would to see with Datadog is that the graphical user interface sometimes takes a little bit to load, especially when diving deep on a subject, and just a little bit more caching would help.

The largest pain point we've had with Datadog to this point was onboarding. This was partly our fault because our logs weren't really set up to be used in a modern observability platform Datadog, but I definitely would have liked to have seen more comprehensive onboarding. We had a few appointments, but the more help we get up front, the easier it is for us to get more familiar and do more things with Datadog.

At this time, I do not think there are any other improvements Datadog needs that would make my experience even better.

I have been using Datadog for approximately four months now.

Datadog is very stable.

We have not yet hit the use case to evaluate Datadog's scalability, but based off of everything else we've used with the infrastructure, I don't think there are going to be any issues with it. We did, as a trial, engage the AWS integration, and immediately it found all of our AWS resources and presented them to us. In fact, it was talking about costing and billing which we had not anticipated, but we were pleasantly surprised with.

Customer support is excellent; I have opened and closed probably five tickets in the past few days, specifically within the past seven days. Very responsive, and the support techs are knowledgeable and responsive.

I would rate customer support an eight out of ten. The only issues that we had were really needing more educational resources to begin with to truly understand the specifics of log management and APM tracing setup, simply because those are very complicated procedures. Walking through that a couple more times with the support engineer probably would have been helpful. It was not a deal breaker or a significant pain point, but the quicker we get up with Datadog, the happier, the quicker and deeper we get with Datadog, the happier people seem to be at our organization.

Overall, the entire Datadog comprehensive experience of support, onboarding, getting everything in there, and having a good line of feedback has been exceptional. I've been in the industry over 20 years, and part of my roles has always been customer-facing. I find that Datadog's client support is very engaging, comprehensive, and thorough.

Positive

For on-prem infrastructure monitoring, we're currently using Nagios, but that's beginning to fade as we rely more on Datadog for our infrastructure monitoring. We had used New Relic for application performance monitoring, but because of the cost associated with that and not seeing the value from it, we stopped using that about two years ago.

We did not purchase Datadog through the AWS Marketplace; we were contacted independently by a Datadog sales agent.

My experience with pricing, setup cost, and licensing has been overall fairly positive. The on-demand/reserved pricing, we were not as cognizant as to how big the on-demand could get, especially when we were getting everything set up, but Datadog proactively took a strong hand in guiding us to getting our costs under control. I'm proud to say that we are within 1% of our projected cost budget, so that was very handy and that's happened in the last month. Very efficient and very effective working with Datadog to control cost.

In terms of time saved, I've noticed that when we're responding to potential errors or during our software deployments, it's saving us minutes at a time that quickly add up to hours, that quickly add up to days in terms of retrieving debug and application error information.

Before choosing Datadog, we evaluated other options including New Relic and SolarWinds.

I would advise others looking into using Datadog to evaluate it against other competing properties and applications in the space, and really dig in. You will find that Datadog does what it's supposed to do very quickly, very efficiently, as does it more cost competitively than some of the other offerings.

Datadog is deployed in my organization in both on-prem and in public cloud scenarios.

On a scale of one to ten, I rate Datadog a nine overall.

I think the most important feature for me in Datadog is the RUM features.

I check the efficiency of the applications that I'm supporting in Datadog and also use it to view the sessions of users.

I have some trouble doing troubleshooting in our app currently, but RUM is my main use case in Datadog.

The personalized dashboards and alerting in Datadog stand out to me, so that way you can gear your use of the product towards what's important to you.

Datadog has allowed us to ensure that we can look at how our beta testers are using our new UIs and seeing where their frustration points are, which has been important to us.

We've been using the heat map feature in Datadog to measure those frustration points.

Some templates for certain roles and things that users care about could be auto-suggested for a dashboard or alerting in Datadog.

We had limitations around RUM and our feature flag provider in Datadog because it's a back-end forward feature flag usage in our Next.js application. We had trouble hooking up our feature flags due to RUM being client-side only. This issue arose because Next.js is a front-end and back-end focused application, and it would be beneficial to send the feature flag resolution from the back-end if needed. Our feature flag provider is GrowthBook, and the way we would have to get those feature flags into Datadog was time-consuming with a lot of boilerplate. We would have to mimic feature flag resolution on the client side, so we decided to forego that.

We have been using Datadog for about two or three months.

Datadog seems stable in my experience without any downtime or reliability issues.

Datadog is scalable and I don't think we'll have problems with scalability in terms of our use case. We might face limitations with logs, but I feel we would not be reaching any of Datadog's limits.

The customer support has been one of the best parts of Datadog.

I would rate the customer support from Datadog a 10 on a scale of 1 to 10.

I would suggest staying in close contact with your customer support representative to get the most out of Datadog.

Positive

We did not have a different solution before Datadog.

Setup with Datadog was pretty easy.

It is too early to tell if we've seen a return on investment so far with Datadog.

I'm not clear on pricing, but it's not a huge concern for us at the moment in terms of RUM. For the other pieces, I know that there may be some pricing that they've been looking at for APM and logs.

I did not evaluate other options before choosing Datadog.

I personally don't use the personalized dashboards and alerting, but I've seen some nice use cases from others on my team. On a scale of 1-10, I rate Datadog an 8.

My main use case for Datadog is application monitoring and alerting.

A specific example of how I use Datadog for application monitoring and alerting is monitoring for storage filling up.

I also monitor services to ensure that they're running when they should be, and then I schedule downtimes for whenever they shouldn't be.

In my experience, the best features Datadog offers are integrations with ServiceNow and PagerDuty and the large variety of other third-party integrations.

The integrations with ServiceNow and PagerDuty have helped my workflow because whenever there's an issue, we can get notified quickly, and whoever is on call, if it's after hours, can be notified that there's an issue going on.

Dashboards are nice for quick and easy access to important and useful information, and logs are a great place to review information quickly and easily without connecting to the application directly.

Datadog has positively impacted my organization by allowing for a more proactive response to issues whenever they occur.

Being more proactive has helped by reducing downtime and improving our response to resolution. It has helped us limit business impact whenever there are issues that arise.

I believe Datadog could be improved because sometimes it's not the most user-friendly, and when monitors have a new metric or a service that no longer needs to be monitored, it remains in the system. It could be user error, but it would be nice to remove a specific service or part of a monitor from continuing to be monitored if there's no data being collected anymore.

Documentation sometimes is a little misleading or confusing, and there are multiple versions available, so having more up-to-date or clearer documentation regarding which version it applies to would be good.

I have been using Datadog for two, two and a half years.

Datadog is stable.

Datadog's scalability has been pretty scalable from what we've done in our organization.

The customer support is very good; it's easy to get support on pretty much any question that we have, including being able to chat in.

Positive

We previously used LogicMonitor, and I was not involved in the discussions on why we switched.

It's a pretty steep learning curve to start using Datadog; it takes time to really configure everything.

I would say we have seen a return on investment, but I don't have any relevant metrics.

My experience with pricing, setup cost, and licensing is that it was good; I wasn't too involved with it, but as far as I know, it was smooth.

Before choosing Datadog, we did evaluate other options, but I'm not sure what those options were.

On a scale of 1-10, I rate Datadog an 8.

My main use case for Datadog is monitoring and collecting metrics. I use it to collect metrics from Kubernetes pod CPU and memory usage, and also logging, basically all our middleware platforms.

The best features Datadog offers are the ability to collaborate between different metrics such as logging, metrics, and APM, which helps me to pinpoint when I'm troubleshooting issues. The dashboard is very useful; I can use it to get a glance on how the system performs, and alerting is what I'm using right now to send notifications to either email or PagerDuty.

Datadog has positively impacted my organization by shortening our time to resolve incidents because it's a central place for getting all the data that we need for troubleshooting.

I think Datadog can be improved by adding anomaly detection, that would be nice. The user interface is okay, but sometimes cost is the issue because for logging, I had to actually trim down my logs because the cost is too much.

I have been using Datadog for several years.

Datadog is stable.

Datadog's scalability is quite good since it's a SaaS solution, and there are no scalability issues for me. I simply install an agent for whatever new component, server, or host I want to monitor, and then I'm good.

The customer support is hit and miss. Sometimes they respond fairly quickly, but it depends on the person, and it may take a couple of communications for them to actually understand what I need.

Positive

I previously used some open-source solutions from other vendors before Datadog. The switch was made to get a better observability stack.

My experience with pricing, setup cost, and licensing indicates that the pricing is based on usage. When we adopt more, we get more, so everything is based on our desire to improve adoptability for the entire studio, then cost becomes a main issue.

Before choosing Datadog, I evaluated other options, including Dynatrace, which was approximately 10 years ago.

My advice to others looking into using Datadog is that if cost is not a concern, I would recommend them to use it. However, if they are sensitive or concerned about how much money they want to spend, then maybe Datadog is not the solution for them.

I would rate Datadog overall as eight out of ten, though I find it too costly.

My main use case for Datadog is the security aspect of it, utilizing the SIEM and the cloud security features. I use it every day monitoring different types of logs and reports that come through, managing most of the alerts that populate from our different applications and software, and it's been a good ride.

Datadog has impacted my organization positively because it tracks all the logs and helps us utilize our features through security. We use Datadog in basically all of our other teams, including engineering, code, APIs, and many other features available, and my peers always say something good about it.

Datadog has helped my organization improve a lot of response time because we get alerts the minute it happens, which is our only means to reduce incident response time. I also appreciate how it provides remediation efforts, allowing us to implement different playbooks while constantly updating with new threats and vulnerabilities, keeping us safe.

One of the best features I appreciate is the Cloud SIEM, and I've used many SIEMs in my experience, but until I got to this company, I never had the chance to really see how Datadog works. With this organization, they were able to show me how easy it was, and Datadog has a really good UI that's easily navigable, helping us teach new team members quickly.

My experience with the Cloud SIEM specifically is that it works 24/7 and stands out due to the easy UI it provides, which helps onboard new members who enjoy it. They are able to pick it up quickly without any prior knowledge.

Datadog helped us out with cloud security features and alerts during situations where we get numerous account lockouts or accounts being jeopardized. Datadog was able to find the alerts and trigger to notify our team in a very prompt manner before it got worse, allowing us to promptly adjust and remediate the situation in time.

Something I would appreciate seeing from Datadog is more events focused on the networking aspect, which allows me to see what others are using. I enjoy showing up to those events and exploring new features they are releasing as well.

I think Datadog has been performing excellently with no areas that need improvement, as they've been doing great and I want them to keep striving to do better.

I'm fairly new with Datadog, having used it for the past year and a half, almost two years now, and it's been going really well.

Datadog is very stable, as there hasn't been any downtime or issues since I've been here, and it's always on time. I would appreciate seeing it as an app or mobile app for quicker issue tracking.

Datadog has definitely kept up with our growth.

I've had a couple instances where I reached out to Datadog's support team, and they have been really super helpful and very kind, even reaching back out after resolving my issues to check if everything's going well.

Positive

I was not here during the time they onboarded Datadog or looked for different solutions, so I'm not aware of which solution we used before.

I cannot share any metrics regarding return on investment.

Pricing is fairly affordable, and the setup cost has been good, while licensing has been well maintained, making it pretty great.

I'm certain they did their research and looked around at many different options, but I cannot speak on their behalf regarding which they chose or had competition with.

My advice for others looking into using Datadog is to honestly give yourself a week or two to explore all the features and software application, as there are quite a lot of amazing features to learn and utilize, making it not just a software to monitor threats but also a tool to enhance your knowledge in this industry. I rate Datadog 10 out of 10.

Our main use case for Datadog is that we heavily rely on it for our infrastructure monitoring and application monitoring, including some of the browser-based application monitoring, which is RUM.

A specific example of how we use Datadog for monitoring is that we monitor our infrastructure CPU and memory utilization. Sometimes we see slowness and figure out CPU utilization was near the threshold, around 90-95%, which helped us to resolve the issue, underlying SQL problem, and that helped us to troubleshoot the issue.

In addition to our main use case, we also use RUM monitoring and synthetic monitoring, which really help us to look at our end-user sessions and proactively solve any slowness or errors spiking up.

The best feature that Datadog offers is infrastructure monitoring, where it can look at the CPU utilization, different process utilization, all the processes which are running, and alert us in advance if things are going beyond normal threshold.

I think everything about the features of Datadog is amazing. Datadog provides details up to the transactions. We can look at the transaction log too for the application, which is really helpful.

Datadog has impacted our organization positively since we were previously using AppDynamics and then we switched to Datadog. It has improved a lot in our alerting and monitoring in the infrastructure space and application space. We can monitor business transactions and take proactive action. It is really great to take actions on the issues before an end user reports it, which is a great advantage for us.

The world is moving toward artificial intelligence, so maybe we can have an inbuilt AI agent within Datadog, or maybe it exists and I have not used it.

The AI aspect would be great where we would not need to go and look at different transactions or different modules of Datadog, as AI can actually provide the data to us on Datadog UI. If we need more details, it could have a link to go to that specific module to look at more details for the application and infrastructure monitoring and alerts.

I have been using Datadog for three years now.

Datadog is stable for our organization, and we have not seen any downtime or issues so far.

Datadog's scalability has been great as it has been able to grow with our needs. As per our need, we are able to utilize different modules and there was never any need where we needed to scale anything else. We have limited our transition recording to 45 days, which helps. That is what our need is. It is really helpful and nothing additional is needed.

We reached out to Datadog only once to find out our AMI images, which we needed for our infrastructure as a code component, and it was a great experience. We got the required information and that helped us.

Neutral

Before Datadog, we previously used OpsRamp and also AppDynamics, and both of the tools we retired and moved to Datadog due to our enterprise approach to consolidate overall monitoring to Datadog.

I gave Datadog a nine out of ten because it is amazing. All the features and functionalities are amazing. The ease of implementation was a bit difficult for us for the database servers where we have different kinds of databases. We needed different kinds of agents to be installed, and that was a bit tricky for us. I think it is not on Datadog but it is about our complex infrastructure where we have a different set of infrastructure in place, so that created a bit of trouble during the implementation.

Since using Datadog, we have seen a return on investment with a lot of savings around infrastructure monitoring, and also on the people needed to monitor overall application and infrastructure on both sides. Previously we had thirteen contractors doing the monitoring for us, which is now reduced to only five. That is a huge saving.

We did not evaluate other options before choosing Datadog, we went with Datadog directly.

My advice for others looking into using Datadog is to keep exploring the tool and utilize the different modules and the different functionalities of features Datadog offers. There are multiple features and functionalities available with the Datadog agents which are really helpful and powerful to troubleshoot, alert, and monitor both applications and infrastructure.

So far, all the features I have used in Datadog are amazing. It captures all the logging information which I have, and I can include the links of Datadog transactions on my Splunk logs. It is integrated with Splunk and other platforms, which is great.

On a scale of one to ten, I rate Datadog a nine.

My main use case for Datadog is dashboards and monitoring.

We use dashboards and monitoring with Datadog to monitor the performance of our Nexus Artifactory system and make sure the services are running.

The best features Datadog offers are the dashboarding tools as well as the monitoring tools.

What I find most valuable about the dashboarding and monitoring tools in Datadog is the ease of use and simplicity of the interface.

Datadog has positively impacted our organization by allowing us to look at things such as Cloud Spend and make sure our services are running at an optimal performance level.

We have seen specific outcomes such as cost savings by utilizing the cost utilization dashboards to identify areas where we could trim our spend.

To improve Datadog, I suggest they keep doing what they're doing.

Newer features using AI to create monitors and dashboards would be helpful.

I have been using Datadog for six years.

Datadog is stable.

I am not sure about Datadog's scalability.

Customer support with Datadog has been great when we needed it.

I rate the customer support a nine on a scale of 1 to 10.

Positive

We did not previously use a different solution.

In terms of return on investment, there is a lot of time saved from using the platform.

I was not directly involved in the pricing, setup cost, and licensing details.

Before choosing Datadog, we evaluated other options such as Splunk and Grafana.

I rate Datadog an eight out of ten because the expense of using it keeps it from being a nine or ten.

My advice to others looking into using Datadog is to brush up on their API programming skills.

My overall rating for Datadog is eight out of ten.