Datadog Reviews

We primarily use the solution for monitoring and log analysis.

Datadog shows all the logs for the services, and it is very useful for troubleshooting.

The most valuable aspect of the solution is the APM.

The logging capabilities are quite useful. 

The logging could be improved in the future. 

I've used the solution for four years.

We use actual user monitoring and have set up thresholds for alerts to PagerDuty, Sentry, Slack, and so on. We also have dashboards set up for tracking latency and error rates. 

As an individual contributor, I also try to set up dashboards for the individual feature projects I work on. I'd like to learn more ways to use this, though, especially when it comes to more proactive approaches to issues. A starter pack of common-use types would be nice.

The solution it has improved our organization by expanding the awareness of issues and alerts beyond SRE and really empowering software engineers at a team level to make changes to monitoring and incident responses.

There could still be more training to bring this even further. A lot of the time I get into Datadog and it's already an incident and I am not in the right mindset to learn about the product or set alerts up.

The feature I have found most valuable is when I can reuse existing monitors and alerts for new dashboards. 

It is nice that things are so integrated, and any individual thing I build out can likely be re-used across the suite.

Other features I have found useful include the stack traces, especially when it links back to something specific I can look for in the code base. I also like that you can group similar alerts together to look for trends over time instead of one in isolation and see if there have been regressions.

The biggest improvement would be around educational content and helping new users get started. I've only been using Datadog for a few months, and at first, it was frankly overwhelming in terms of both the UI and the available capabilities. The workshops today have helped with this, however, more could be done.

As a user, I have about six or more months of experience with the solution. As a company, I'm not sure.

I was not in charge of evaluating any other solutions.

We use the solution for testing all of our application's endpoints. It is making sure that they work on a consistent basis.

We enjoy the multistep API tests.

They need to implement template variables into the message response body. They could be injected in the subsequent calls. However, they fail to be able to use those variables anywhere in the alert body message that is sent out.

We've been using the solution for a year.

I've never thought about stability and have no insights.

I find we are getting tossed from engineer to engineer. It is not fun when you have an ongoing problem. That is something from the customer resolution team that needs to be addressed.

Positive

We previously used Selenium. I was forced to use it. However, Datadog was a way simpler solution to setting up browser and API tests quickly.

The solution is very straightforward since it has a good GUI.

The initial setup was handled in-house.

It is not my job to track the ROI.

I have no details about the pricing. 

We did not evaluate other solutions. 

The solution is a SaaS.

We are using the solution for scaling up the website for market data applications. EC2 and Datadog have enabled high-level monitoring of underlying infra and services.

The Datadog profiler comes in handy to pinpoint issues with resource utilization during peak hours, and traces/log management helps narrow down the root cause.

The network map is crucial in identifying bottlenecks and determining what needs more attention.

Host map helps identify problematic hardware and devise ways to counter issues that arise during scaling, and deploying solutions on the cloud.

While my team is relatively new to Datadog, I already see immense value in switching over to Datadog as the primary APM and NPM tool.

The arsenal of features it offers is bound to come in a clutch when facing production issues, and when finding out what went wrong is crucial.

The network map has helped to figure out the golden signals and optimize the infrastructure.

The synthetics have helped ensure the high availability of arch functions as intended.

The network map is useful. With it, we have the ability to see the data flow across the entire network path across all the applications is highly valuable as the data from this service helps identify network bottlenecks, non-performant applications, and bad endpoints.

This is especially crucial for a high-availability website aimed at market data applications where low latency is crucial.

The host map gives a clear picture of the entire infrastructure, and the ability to switch between logs, metrics, and traces is very handy when it comes to debugging issues on the fly.

I love the ability to install the integrations and agents quickly. This is a well-made product.

To be very fair, I haven't had enough experience with Datadog to pick out improvements.

My involvement with Datadog has largely been positive. I love the simplicity and intuitiveness it offers - even for nontechnical folks who just might be starting out with developing technical chops in their domain.

I've used the solution for three years.

We use an enterprise version of a CMS platform which is enabling businesses to transmit content to their customers. The tool is fully customizable to the end user, including out-of-the-box integrations as well as APIs for custom plugin support. 

Our systems fully manage content using AWS as the back-end cloud provider. Assets are kept in secure buckets and utilize the Kubernetes infrastructure to deliver our product to end users and internal authors. Using the CMS allows for business people to manage content without needing development efforts.

This tool is the sole purpose of my company and the solutions we provide around it. Enabling customers to manage their content in a fast, reliable, and highly user-friendly setup has been critical to our success. 

Offering our product at SaaS, PaaS, cloud, and on-prem editions has enabled us to provide a solution for all types of customers. 

The platform appeals to companies spanning many industries on a global scale. 

Being based in SUI allows us to secure both the EU and other companies more easily.

The enterprise version of a CMS platform enables businesses to transmit content to their customers. 

The tool is fully customizable to the end user, including out-of-the-box integrations as well as APIs for custom plugin support. 

The content is fully managed within our systems using AWS as the back-end cloud provider. Assets are kept in secure buckets, and we can utilize the Kubernetes infrastructure to deliver our product to end users and internal authors. 

Using the CMS allows for business people to manage content without needing development efforts. Allowing this type of setup for business users has been a key reason for our success.

There is always room for improvement when dealing with cloud-based technologies. Mainly, I would say, it's just increasing our offerings to attract various other types of industries and businesses across more fields. 

New features as requested by our existing customers will help make the product better.

The product was self-developed.

We use a SaaS deployment. 

We primarily use the solution for the RUM, security monitoring, and streams.

We need to monitor users and what they access. We also need to identify security loopholes and attack patterns and identify and quickly respond to issues.

We can identify pushbacks, and get insight into application components that stack up with each other. We can understand which components, libraries, and code to alert teams.

Using Datadog, we can raise incidents, track incidents to completion, and be able to gather data for reporting and post-mortem.

The solution allows us to track fixes and tracks their test coverage. With it, we get confidence in the fix/improvement phase and be able to provide a response.

The solution has improved the organization by providing good insights into app performance and offering good dashboards.

With it, our company can track fixes and track test coverage. We get confidence in the fix/improvement and are able to provide a response.

I've been able to present data to the team/ management based on the team's dashboards.

It's helped us when we've needed to monitor users and what they access or needed to identify security loopholes and attack patterns. It can help identify and quickly respond to issues.

Datadog allows us to identify pushbacks, and get insight into application components (how they stack up with each other). When we need to know which component, libraries, code, and teams to alert, we can raise and track incidents to completion and gather data for reporting and post-mortems.

The APM and container monitoring are excellent aspects of the solution.

It helps with monitoring users and what they access.

We can identify security loopholes and attack patterns while quickly responding to issues.

Our team can now identify pushbacks and get insights into application components. We can gather data for reporting and post-mortem, and we can track fixes and test coverage. Datadog allows us to gain confidence in the fix/improvement.

I've been able to present data to the team/ management based on the team's dashboards.

We'd like Datadog to make the log storage cheaper. Right now, it makes our life difficult since logs are stored separately.

We should not have to rely on team members to educate themselves in Datadog features. There should be templates that anyone can select, and they should be able to create dashboards easily. This is really slowing us down. It takes time to to explore the full potential of Datadog.

I've used the solution for two years.

After a security incident, we needed to find and migrate to a different cloud provider, and after evaluating different competitors and the skill set of the team, we decided to move to AWS. AWS also enables the team to have finer control over how our apps are deployed and how security and access are managed. By leveraging AWS's functionality, we have increased our application's security and sped up the deployment process. We've even been able to handle higher workloads due to AWS's auto-scaling functionality.

Elastic container services have improved our organization by allowing us to deploy our application. While this problem was not solved by using the elastic container service since we had a previous solution on a different provider, the ease and flexibility of deploys have greatly benefited the ops team and the overall engineering organization. It is easy to use. However, there are many out-of-the-box features like metrics and seeing task definitions that make life easier.

The most valuable feature I have found is the elastic container service. That is where our apps get deployed. This feature is really important to us since, without it, we would not be able to deploy our apps the way we wanted to and would have to use a different vendor. 

This service is also valuable to our team as we have a lot of familiarity with it and adapting to the services from our previous one was fairly seamless. 

Another feature that is very valuable for our team is the IAM. It allows us to control security.

ECS could be improved by including more tutorials for beginners to reduce the barriers to entry. It would help to ensure understanding and learning in terms of how to use a cloud provider. Besides this, there are not any other areas of improvement needed since the service is very straightforward and there is ample documentation.

I've used the solution for one year.

We use the solution for logs from all our applications. In Datadog, for monitoring logs, our team creates an automation for implementing massive logging in all our systems. Now, we are deploying it in our core systems.

We are using it to indicate issues and alert our operations team. With this, we better monitoring of our applications and logs.

However, the main difficulty is implementing the solutions in our Kubernetes cluster, separated just as logs to the specific namespace as the volume of logs is tremendous.

The solution is useful for monitoring logs. 

We can create an automation for implementing across all our systems. Right now, we are deploying it in our core systems.

The greatest value is integrated monitoring as it is able to quickly detect issues and improve our time to market.

Our main challenge is implementing the solutions in our Kubernetes cluster, separated just as logs to the specific namespace since the volume of logs is tremendous.

I've used the solution for one year.