Datadog serves as my primary tool for infrastructure monitoring and log analysis in a cloud environment. From a network and security perspective, I use it to monitor server health, track network metrics like latencies and traffic patterns, and analyze logs for troubleshooting issues such as VPN instability and unexpected spikes. The ability to correlate metrics and logs in one place makes it much faster to identify the root cause instead of checking multiple tools.

One example where Datadog proved invaluable was during a sudden spike in application response time. We received alerts on increased latencies, and instead of checking multiple tools, I used Datadog's dashboard to quickly correlate metrics. I noticed that while the application CPU was normal, there was a spike in database response times. Using the logs and metrics together, I was able to confirm that the issue was coming from the database, not the application. This helped us quickly involve the right team and resolve the issue faster.

The best features of Datadog are the correlation capabilities and unified visibility. The most useful aspect is that I can see metrics, logs, and service-level data in one place. During troubleshooting, I do not have to switch tools; I can directly correlate spikes in latencies with log error patterns, which saves considerable time. Another feature I find very useful is the dashboards, which are flexible, and I can create views based on what I actually need to monitor daily instead of relying on default setups. The integration with cloud services makes onboarding very easy, and once integrated, most of the data starts flowing automatically without much manual effort.

Datadog has had a positive impact, mainly by improving how quickly we detect and understand issues. Earlier, when something went wrong, considerable time went into figuring out where the problem actually was. Now, with better visibility across services and logs, we can quickly narrow down the source, whether it is application, infrastructure, or dependency-related. It has also helped in reducing the back and forth between teams because we can validate issues with the data before escalating, which has made incident handling smoother and more efficient overall.

One area where Datadog can be improved is around alert quality. In the beginning, it tends to generate many alerts, and without proper tuning, many of them are not actionable. It would help if there were more built-in guidance or smarter defaults to reduce noise. Another improvement area is cost visibility and control. As log and metric ingestion increases, it has not always been straightforward to track which data is driving the cost. More granular and real-time cost insights would make it easier to manage. Additionally, while the dashboards are flexible, navigating and organizing them at scale can become slightly difficult. Better structuring or management options would help in larger environments.

I have been using Datadog for nearly two years.

Datadog has been stable overall in my experience. We have not seen any major platform outages. Metrics collection and alerting have been consistent in day-to-day use. Most issues we have faced were related to configurations or alert tuning rather than the platform itself. The platform is stable with no major platform issues, only configuration-related challenges.

Datadog scales well as environments grow in my experience. As we add more servers and services, onboarding is straightforward with agents and integrations. We have not faced any major performance issues from the platform side; it handles increased metrics and monitoring loads smoothly. The primary consideration is managing log volume carefully because as the scale increases, data ingestion and costs also go up. Datadog is scalable technically, but the ingestion costs need to be managed as the environment grows.

We do not rely on Datadog support for day-to-day issues. Most of the time, we are able to resolve things using the dashboards, logs, and their documentation. We have only reached out in a few cases, mainly for configuration-related queries, and in those situations, support was helpful, though sometimes it required a few back and forth interactions to get to the exact solution. Overall, support is decent, but we mostly depend on self-troubleshooting.

Before Datadog, we were mainly using native cloud monitoring like Azure Monitor, along with a few basic tools. The main issue was that monitoring was fragmented. Metrics, logs, and alerts were spread across different places, and so during an incident, we had to switch between multiple tools to understand what was happening. We moved to Datadog to have everything in one place. The ability to correlate metrics and logs in a single platform made troubleshooting much faster and more efficient.

Setting up dashboards and integrations in Datadog is relatively straightforward in my experience, especially for standard cloud services. For integrations, once we connect our cloud account, most of the metrics start coming in automatically, so the initial setup is not very complex. The documentation also helps considerably during this phase. For dashboards, basic ones are easy to create using existing templates, but to make them truly useful, we have to spend time customizing them based on our actual use cases, like adding specific metrics and refining the layout. Overall, the initial setup is easy, but making it truly effective takes practical tuning.

We have seen a clear return on investment with Datadog, mainly in terms of time saved and faster incident handling. For example, earlier when an issue occurred, it would take around thirty-five to forty-five minutes just to identify the root cause because we had to check multiple tools. With Datadog, we are usually able to narrow it down within ten to fifteen minutes using the centralized dashboard and logs. We have also reduced repeated troubleshooting efforts because we can identify patterns and fix the root cause instead of dealing with the same issues repeatedly. It has not reduced headcount, but it has definitely improved team efficiency and allowed us to handle more incidents with the same team.

My experience with pricing for Datadog has been mixed. The initial setup cost is relatively low since it is a SaaS model and does not require a heavy upfront investment. Getting started is quite quick with agent-based deployments. However, the ongoing cost is something that needs to be managed. Pricing is mainly based on data ingestion, such as logs, metrics, and traces, and it can increase quickly if everything is enabled by default. Licensing is flexible, but it requires continuous monitoring and optimization to keep costs under control.

One additional point I can add is that with Datadog, I focused considerably on making alerts actionable and reducing noise. In the initial phases, we had too many alerts that were not very useful, so we spent time tuning thresholds, adding conditions, and correlating alerts with real impact. After that, alerts became much more meaningful and helpful in faster response. I also use it regularly for trend analysis, checking for recurring spikes or patterns over time, which helps in identifying potential issues before they become incidents.

The features of Datadog become truly useful when you start combining them, not just using them separately. For example, just looking at the metrics alone does not always give the full picture, but when you combine metrics with logs and service-level data, it becomes much easier to understand what is actually happening during an incident. Features like tagging help considerably in filtering data across environments and services, especially when the setup grows. Without proper tagging, it can get difficult to navigate. Overall, the strength of Datadog is not just the individual features, but how well they work together in real scenarios.

We have seen noticeable improvements after using Datadog, mainly in terms of time saved and faster incident handling. Earlier when an issue occurred, it could take around twenty to forty minutes just to understand where the problem was. Now, with the centralized visibility and correlation of metrics and logs, we are often able to narrow it down within fifteen to twenty-five minutes. We have also seen fewer repeated incidents because we can identify patterns and fix the root cause instead of just resolving symptoms. Incidents are getting resolved faster, and the time spent on troubleshooting has reduced significantly.

My advice for anyone considering Datadog is to be selective about what you monitor from day one. It is tempting to enable everything, but that usually leads to too much data and noisy alerts. Instead, start with critical services and key metrics, and then expand gradually. Invest time in tagging and structuring your data properly because it makes a considerable difference later when you need to filter, troubleshoot, or build dashboards. Finally, review your setup regularly because what works in the beginning may not stay relevant as the environment grows. Start small, avoid collecting all data, use proper tagging, and keep refining your setup over time. This review reflects an overall rating of eight.

My main use case for Datadog is infrastructure and log monitoring in a cloud-based environment. From a network and security perspective, I mainly use it to monitor server health, track network-level metrics, and analyze logs for troubleshooting issues such as VPN instabilities, traffic spiking, or unexpected behavior.

One recent example where I used Datadog was during a VPN-related issue where users were reporting intermittent disconnections. I checked our Datadog dashboard and noticed spiking in network latencies and a sudden increase in connections dropped around the same time users reported the issues. I then correlated this with the logs and found that one of the back-end servers handling the connection was hitting high CPU utilization. Because everything was centralized, I did not have to jump between multiple tools. I was able to quickly identify the impacted servers and escalate it to the infrastructure team. Once the load was balanced, the issue got resolved.

With Datadog, I mainly focus on creating meaningful dashboards and tuning alerts properly. In the beginning, we saw a lot of alert noise, so we had to refine thresholds and conditions to make sure alerts are actually actionable. Once that was done, it became much more effective for proactive monitoring instead of just reactive troubleshooting.

One of the best features of Datadog, in my opinion, is its unified visibility across the metrics, logs, and traces in a single platform. The dashboards are very flexible and customizable, which helps a lot in creating meaningful monitoring views based on different use cases. I also find the log management quite useful because it allows quick correlation with metrics during troubleshooting. Another strong feature is its integration, especially with cloud platforms such as AWS or Azure, which makes onboarding and monitoring much easier without heavy manual work.

Integration with cloud platforms such as Amazon Web Services or Microsoft Azure has really made daily monitoring much easier. Once the integration is set up, Datadog automatically pulls metrics from services such as virtual machines, load balancers, and databases without needing manual configuration on each resource. In one case, I was monitoring a cloud-based application where we started seeing performance issues through Datadog's Azure integrations. I could quickly view metrics from the application server and the back-end database in the same dashboard. It helped me identify that the issue was not network-related but due to the increased load on the backend services. Instead of checking multiple portals, everything was available in one place, which saved time and made troubleshooting faster.

Datadog has had a positive impact mainly by improving visibility and reducing troubleshooting times. Earlier, we had to rely on multiple tools to check metrics and logs, which delayed root cause analysis. With Datadog, everything is centralized, so it is much faster to identify issues and take actions. It has also helped in proactive monitoring with properly tuned alerts. We are able to detect unusual behaviors such as spiking in traffic or resource usage before it turns into a major incident. Overall, it has improved operational efficiency and reduced downtime by enabling quicker responses during incidents.

If you are asking for improvements, I feel some small areas where Datadog can improve. One area is alert management. In a dynamic environment, it can generate a lot of alert noise if not tuned properly. More intelligent alerting or built-in recommendations would help. Another aspect is cost visibility. As log ingestion increases, pricing can scale quickly. Having more transparent and granular cost control features would make it easier to manage usage. Also, the initial setup and configuration can feel a bit complex for new users.

I have been using Datadog for ten months.

In my experience, it has been quite stable; we have not faced any major outages or reliability issues from the platform side. Data collection and dashboards have been consistent, and alerts are delivered on time as long as they are properly configured. Most of the issues we have seen were related to configuration or alert tuning rather than the platform itself.

It has scaled well for our needs. As we added more servers and services, Datadog was able to handle the increased load without any major issues. Since it is a SaaS platform, we did not have to worry about backend scaling. New hosts and services get onboarded easily with the agents, and metric collection continues smoothly even as the environment grows. The only thing we monitor closely is log volume because as scale increases, ingestion and costs also go up, but from a performance and handling perspective, it has been quite good.

In my experience, the customer support from Datadog has been quite reliable. For standard issues and queries, the response time is generally good, and the documentation is also very helpful for resolving common problems. For more complex cases, support may take some time for investigations, but they usually provide proper guidance and follow-up. Overall, I would say support is responsive and helpful, especially when combined with their strong documentation.

This is the first time I am using Datadog. Before that, there was not any solution in place.

The initial setup cost is relatively low since it is a SaaS model and getting started is straightforward with agent-based deployments. However, the main challenge is the ongoing cost, which depends on data ingestion such as logs, metrics, and traces. As usage grows, especially with log collection, the costs can increase quickly, which requires proper planning around what data to collect, retention policies, and filtering to keep control. Overall, I think it is flexible, but cost optimization needs continuous monitoring.

We have seen a return on investment with Datadog, mainly in terms of saving operational efficiency. For example, earlier our troubleshooting process involved checking multiple tools, which used to take around forty to forty-five minutes just to identify the root cause. With Datadog, since metrics and logs are centralized, we are usually able to reduce the time to around ten to twenty minutes in many cases. This has improved our response time and reduced the duration of incidents. While it may not directly reduce headcount, it definitely improves team productivity and helps handle more issues efficiently with the same team.

While we do not track exact numbers in all cases, with Datadog we have definitely seen a noticeable improvement in incident response time. For example, earlier it could take around thirty to forty-five minutes to identify the root cause analysis because we had to check multiple tools. With Datadog's centralized dashboards and logs, we are usually able to narrow it down within ten to fifteen minutes in most cases. We have also seen fewer escalations for minor issues because alerts help us catch problems earlier, which indirectly reduces downtime and improves overall efficiency.

We did consider a few alternatives, but they each have their own standards. We considered solutions such as Splunk, New Relic, and Prometheus. Everything is more costly, but I prefer Datadog. I have just heard about Datadog and other monitoring tools from some colleagues. As per their comparisons, I feel Datadog is much better.

If anyone is looking to use Datadog, I would advise planning your monitoring strategy from the beginning. Focus on what metrics and logs are actually important because collecting everything can increase noise and costs. It is also important to spend some time on proper alert tuning; otherwise, you may end up with too many non-actionable alerts. I would also recommend starting with key integrations, especially with cloud platforms, and then gradually expanding use instead of enabling everything at once. I would rate this product an eight out of ten.

Datadog's main use case is end-to-end monitoring that helps check problems across infrastructure, application, database, security, and logs.

For example, when checking a problem with a mobile application such as an error from a user hitting a transaction, we check from the client-side mobile device and also from the back end for the API to see if there is latency or an error that triggers the problem. There may be an issue on the database, such as a locking query or high latency on query performance. For infrastructure, if the application is slow, it may be impacted on infrastructure monitoring by CPU and memory consumption.

Datadog is a powerful observability tool that allows us to correlate and see problems on the infrastructure or application side. In an incident war room, we can see the correlation and the detailed root cause of the problem across real user monitoring, application, database, and infrastructure.

Datadog has positively impacted our organization because our customers are very happy using it. With silo monitoring, where infrastructure has separate monitoring, application has another, and cloud has another, it becomes tricky and complex. We cannot correlate the silo monitoring, and pricing is complicated. With Datadog, we can centralize and use one observability tool for monitoring all components across all features or modules, unifying the monitoring process.

Regarding specific outcomes, I observe that tools with Datadog's capabilities enable us to quickly achieve mean time to detect problems. We can specifically check the root cause analysis of issues from the infrastructure, application, database, or security sides. Mean time to resolve is improved with Datadog since it provides many suggestions and actions to resolve problems, which heavily impacts the business for our application customers when issues arise.

Datadog's best feature is real user monitoring.

I prefer Datadog's real user monitoring most because of its analytics capabilities. First, Datadog is recognized in the Gartner Digital Experience for real user monitoring. Second, the analytics capability is very powerful, enabling us to check the experience of customers first. We can also correlate with the back-end side of the performance for real user monitoring and application monitoring. Finally, the capability of metrics within real user monitoring provides many helpful insights for mobile developers to improve their mobile application performance.

Datadog could improve its pricing because it is very tricky, and most of our customers notice many hidden costs. Additionally, if possible, Datadog should offer deployment options not only for SaaS but also for on-premises solutions, which would benefit banking transactions.

Regarding pricing, it remains tricky with many hidden costs. For technological enhancement, there could be an on-premises option alongside the SaaS version. I also find setting up and configuring Datadog to be very complex.

My experience with pricing, setup costs, and licensing is that it is very tricky due to many hidden costs, so we need to check repeatedly for allotments and commitments regarding what we receive from the license.

My advice for others looking into using Datadog is to initially simplify the technical setup and configuration. Secondly, regarding pricing mechanisms, it would be wise to commit to clear allotments to avoid hidden costs for customers, as it significantly impacts pricing.

I believe Datadog is the largest single observability platform, with correlation as a differentiation factor, enterprise readiness as a measure, and cost management now being a key topic with a very clear roadmap and direction. I would rate this product nine out of ten.

My main use case for Datadog is that we offer the application performance management service within PwC as a global team.

A specific example of how my team uses Datadog for performance management is that my team does not directly use Datadog for performance management; however, we work with approximately 300 teams that use it daily for monitoring their apps. One of the most used cases is to observe when services are up and down and if services are not degraded.

We use most of every product within Datadog across the 300 customers that we have internally.

Datadog has positively impacted my organization because before Datadog, we had multiple APM tools and monitoring tools, which fragmented the service. The reason was that some tools offered benefits to certain teams, while other tools offered different benefits to other teams. With Datadog, we managed to get everyone on board into a single place and a single tool, providing teams with one spot where they can check everything related to monitoring, and enabling management and leadership to have an overview of all tools working together.

I measured the impact of bringing everything into one place through observation, and I can confirm that efficiency in reporting improved dramatically and it became much easier to observe changes. Standardization was a tremendous win for us. Having a set of standard alerts and monitoring in place allowed us to speed up onboarding for every app. Once the resources are in Datadog, the system provides alerting out of the box. Additionally, cost has decreased dramatically.

Datadog's best features include very high demand for logs management for alerting on indexed logs and a shift towards Flex Logs for storage and long-term storage. Most recently, BitsAI and the LLM part within Datadog has been in focus for us.

Flex Logs has helped my teams because we are migrating from other services to have a unique place to store all the logs, the non-security logs, and the app logs. This has benefited those teams because they also benefit from other services within Datadog such as APM or other monitoring solutions. By bringing the logs into Datadog, they now have a single place where they can correlate everything.

The LLM integration within Datadog has helped my teams because LLM usage is at the beginning stage right now, and people are very excited. We have all these AI and LLM-based tools, and having the option of monitoring them is a great benefit for us. However, we are in the exploratory phase of this process and have just begun.

BitsAI is very interesting; we have done some testing and we are going to promote it and use it in our production environment. This is a very exciting new tool for us.

Datadog can be improved because sometimes it seems it has not been developed for enterprises. We work with over 300 customers, with each customer having multiple instances or apps within Datadog. We are facing difficulties in controlling access, in privacy settings, and splitting usage and costs for these customers.

We want to be able to customize the cost part, and we would appreciate more granular access control.

I have been using Datadog for four or five years.

Datadog is stable.

We have never had an issue with Datadog's scalability.

Datadog's customer support is good; it could be improved in terms of communication, but it is adequate.

We previously used Grafana, AppDynamics, New Relic, Splunk, and a couple of other smaller, more dedicated tools.

My experience with pricing, setup cost, and licensing is good; nothing out of the ordinary.

Before choosing Datadog, the biggest contender we evaluated was AppDynamics.

My advice for others looking into using Datadog is to test it out and see if it works for you. Try to become accustomed to the tagging part of things, and go through each product to understand what each product within Datadog is offering. I would rate this product an eight out of ten.

My main use case for Datadog is logging security signals and monitoring account activity and suspicious behavior within our company.

For monitoring suspicious behavior, we look for alerts with things like unusual sign-in locations, unusual sign-in times, or registering new multi-factor devices in unusual circumstances or locations.

In addition to that, we also look for patterns and frequency of how often MFA is being prompted from individuals.

The best features Datadog offers include the ability to generate reports very quickly and put in extensive filtering to get very specific information.

The report generation and filtering help me in my day-to-day work by assisting in generating reports for higher-ups and turning data into actionable items.

Since using Datadog, it has positively impacted our organization by giving us a one-stop shop for multiple applications and services that we can analyze in one spot.

Having a one-stop shop has made things easier for my team, and we have seen specific outcomes such as saving a lot of time.

Datadog could be improved if the menu system was a little clearer and less cluttered, making it easier to navigate.

Additionally, more documentation is always beneficial to have.

I have been using Datadog for about three years.

Datadog is very stable.

Its scalability is good, and it has kept up as our organization has grown or changed.

I have not had to reach out to customer support, so I cannot comment on that experience.

I did not previously use a different solution before Datadog.

While I don't have any specifics on money saved, I can say that it has definitely improved our efficiency overall.

My experience with pricing, setup cost, and licensing for Datadog shows that the pricing is very fair and setup has been very simple and easy to do.

Before choosing Datadog, I did not evaluate other options.

My advice to others looking into using Datadog is to read the documentation. I would rate this product a 9 out of 10.

My main use case for Datadog involves working on projects related to our sales reps in terms of registering new clients, and I've been using Datadog to pull up instances of them while they're beta testing our product that we're rolling out just to see where their errors are occurring and what their behavior was leading up to that.

I can't think of all of the specific details, but there was a sales rep who was running into a particular error message through their sales registration process, and they weren't giving us a lot of specific screenshots or other error information to help us troubleshoot. I went into Datadog and looked at the timestamp and was able to look at the actual steps they took in our platform during their registration and was able to determine what the cause of that error was. I believe if I remember correctly, it was user error; they were clicking something incorrectly.

One thing I've seen in my main use case for Datadog is an option that our team can add on, and it's the ability to track behavior based on the user ID. I'm not sure at this time if our team has turned that on, but I do think that's a really valuable feature to have, especially with the real-time user management where you can watch the replay. Because we have so many users that are using our platform, the ability to filter those replay videos based on the user ID would be so much more helpful. Especially in terms where we're testing a specific product that we're rolling out, we start with smaller beta tests, so being able to filter those users by the user IDs of those using the beta test would be much more helpful than just looking at every interaction in Datadog as a whole.

The best features Datadog offers are the replay videos, which I really find super helpful as someone who works in QA. So much of testing is looking at the UI, and being able to look back at the actual visual steps that a user is taking is really valuable.

Datadog has impacted our organization positively in a major way because not even just as a QA engineer having access to the real-time replay, but just as a team, all of us being able to access this data and see what parts of our system are causing the most errors or resulting in the most frustration with users. I can't speak for everybody else because I don't know how each other segment of the business is using it, but I can imagine just in terms of how it's been beneficial to me; I can imagine that it's being beneficial to everybody else and they're able to see those areas of the system that are causing more frustration versus less.

I think Datadog can be improved, but it's a question that I'm not totally sure what the answer is. Being that my use case for it is pretty specific, I'm not sure that I have used or even really explored all of the different features that Datadog offers. So I'm not sure that I know where there are gaps in terms of features that should be there or aren't there.

I will go back to just the ability to filter based on user ID as an option that has to be set up by an organization, but I would maybe recommend that being something part of an organization's onboarding to present that as a first step. I think as an organization gets bigger or even if the organization starts using Datadog and is large, it's going to be potentially more difficult to troubleshoot specific scenarios if you're sorting through such a large amount of data.

I have been working in this role for a little over a year now.

As far as I can tell, Datadog has been stable.

I believe we have about 500 or so employees in our organization using our platform, and Datadog seems to be able to handle that load sufficiently, as far as I can tell. So I think scalability is good.

I haven't had an instance where I've reached out to customer support for Datadog, so I do not know.

I do not believe we used a different solution previously for this.

I cannot answer if I have seen a return on investment; I'm not part of the leadership in terms of making that decision. Regarding time saved, in my specific use case as a QA engineer, I would say that Datadog probably didn't save me a ton of time because there are so many replay videos that I had to sort through in order to find the particular sales reps that I'm looking for for our beta test group. That's why I think the ability to filter videos by the user ID would be so much more helpful. I believe features that would provide a lot of time savings, just enabling you to really narrow down and filter the type of frustration or user interaction that you're looking for. But in regards to your specific question, I don't think that's an answer that I'm totally qualified to answer.

I was not part of the decision-making process before choosing Datadog, so I cannot speak to whether we evaluated other options.

Right now our users are in the middle of the beta test. At the beginning of rolling the test out, I probably used the replay videos more just as the users were getting more familiar with the tool. They were probably running into more errors than they would be at this point now that they're more used to the tool. So it kind of ebbs and flows; at the beginning of a test, I'm probably using it pretty frequently and then as it goes on, probably less often.

It does help resolve issues faster, especially because our sales reps are used to working really quickly in terms of the sales registration, as they're racing through it. They're more likely to accidentally click something or click something incorrectly and not fully pay attention to what they're doing because they're just used to their flow. Being able to go back and watch the replay and see that a person clicked this button when they intended to click another button, or identifying the action that caused an error versus going off of their memory.

I have not noticed any measurable outcomes in terms of reduction in support tickets or faster resolution times since I started using Datadog. For myself, looking at the users in our beta test group, none of those came as a result of any sort of support ticket. It came from messages in Microsoft Teams with all the people in the beta group. We have resulted in fewer messages in relation to the beta test because they are more familiar with the tool. Now that they know there might be differences in terms of what their usual flow is versus how their flow is during the beta test group, they are resulting in fewer messages because they are probably being more careful or they've figured out those inflection points that would result in an error.

My biggest piece of advice for others looking into using Datadog would be to use the filters based on user ID; it will save so much time in terms of troubleshooting specific error interactions or occurrences. I would also suggest having a UI that's more simple for people that are less technical. For example, logging into Datadog, the dashboard is pretty overwhelming in terms of all of the bar charts and options; I think having a more simplified toggle for people that are not looking for all of the options in terms of data, and then having a more technical toggle for people that are looking for more granular data, would be helpful.

I rate Datadog 10 out of 10.