Item: Datadog
Rating: 8
Author: Verified User

Overall Satisfaction with Datadog

Use Cases and Deployment Scope

At our small startup of seven engineers, we use Datadog to centralize observability across our stack. For logging, we aggregate application and infrastructure logs to quickly debug issues with contextual insights. Metrics help us monitor system performance in real time, from server CPU to application-specific KPIs. We’ve created tailored dashboards to visualize key data points for different services, enabling faster decision-making during incidents or deployments. For alerting, we’ve set up threshold- and anomaly-based alerts that notify us via Slack when something goes wrong, allowing us to respond proactively. Datadog keeps our team aligned and efficient without needing a dedicated ops team.

Pros and Cons

Pros

Tracking and grouping errors, with comment history across time
Searching and retaining logs
Creating custom dashboards and alert monitors

Cons

Alert windows cause lag in notifications (e.g. if the alert window is X errors in 1 hour, we won't get alerted until the end of the 1 hour range)
I would appreciate more supportive examples for how to filter and view metrics in the explorer
I would like a more clear interface for metrics that are missing in a time frame, rather than only showing tags/etc. for metrics that were collected within the currently viewed time frame

Return on Investment

Improving confidence in deployments
Faster detection and resolution of errors/issues
Effectively functions as an SRE (we don't have dedicated SREs)

Usability

I rate Datadog’s usability a 7 out of 10 because, while it’s powerful and feature-rich, it can be overwhelming to navigate. The platform offers a vast array of tools—logs, metrics, traces, dashboards, alerting—but the lines between them aren’t always clear. For example, it’s not obvious when to use monitors versus notebooks, or how dashboards differ from the query explorer. This can lead to duplicated effort or confusion, especially for new team members. Once you learn the ecosystem, it’s incredibly effective, but the learning curve and occasional UI complexity hold it back from being truly intuitive out of the box.

Alternatives Considered

Elasticsearch

In terms of usability, I’ve found Datadog significantly more approachable and powerful compared to Elasticsearch, especially for day-to-day operational monitoring. Datadog offers a much more cohesive, user-friendly interface out of the box, with built-in support for metrics, logs, tracing, alerting, and dashboards—all tightly integrated. In contrast, Elasticsearch often felt barebones and required considerable setup and additional tooling (like Kibana or Logstash) to reach the same level of functionality.
While Elasticsearch is excellent for high-volume log ingestion and full-text search, it lacks the depth of features and real-time visualization capabilities that Datadog provides natively. The query language in Datadog is also quite usable and comparable for my needs—mainly filtering and aggregating logs and metrics—without needing to learn Elasticsearch's more complex DSL. Overall, Datadog saves our team time and effort, whereas Elasticsearch often felt like building a monitoring system from scratch. The all-in-one nature of Datadog, despite its complexity, is ultimately more efficient and scalable for our use case.

Key Insights

Do you think Datadog delivers good value for the price?

Yes

Are you happy with Datadog's feature set?

Yes

Did Datadog live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Datadog go as expected?

I wasn't involved with the implementation phase

Would you buy Datadog again?

Yes

Other Software Used

Cursor, GitHub, Slack

Likelihood to Recommend

Datadog excels in microservices environments where visibility across distributed systems is critical. For example, we use it to trace latency spikes across services, correlate logs during outages, and monitor deployments with custom metrics. It’s ideal for real-time alerting—catching memory leaks or sudden traffic drops. However, for large-scale log ingestion, it becomes expensive quickly, making it less ideal for storing high-volume debug logs long-term. Also, Datadog’s UI can be overwhelming for new users, requiring training to navigate effectively. For simpler apps or teams needing only basic monitoring, lighter-weight or open-source tools like Prometheus and Grafana might be more appropriate.

Comments

Please log in to join the conversation