Datadog is a monitoring service for IT, Dev and Ops teams who write and run applications at scale, and want to turn the massive amounts of data produced by their apps, tools and services into actionable insight.
$1.27
per month (billed annually) per host
VictoriaMetrics Community
Score 8.5 out of 10
Enterprise companies (1,001+ employees)
VictoriaMetrics is a high-performance monitoring solution and time series database
N/A
Pricing
Datadog
VictoriaMetrics Community
Editions & Modules
Log Management
$1.27
per month (billed annually) per host
Infrastructure
$15.00
per month (billed annually) per host
Standard
$18
per month per host
Enterprise
$27
per month per host
DevSecOps Pro
$27
per month per host
APM
$31.00
per month (billed annually) per host
DevSecOps Enterprise
$41
per month per host
No answers on this topic
Offerings
Pricing Offerings
Datadog
VictoriaMetrics Community
Free Trial
Yes
Yes
Free/Freemium Version
Yes
Yes
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
Optional
Optional
Additional Details
Discount available for annual pricing. Multi-Year/Volume discounts available (500+ hosts/mo).
Enterprise support prices are negotiated individually with every customer. The price depends on many factors such as:
* Costs for the existing monitoring solution
* The amounts of collected data and the workload specifics (unique time series, churn rate, ingestion rate, query types, query rate, etc.)
* The amounts of compute resources needed for the monitoring solution
* Additional enterprise features
* SLA tier
Contact us at info@victoriametrics.com for more details on the pricing.
A one-stop solution for everything you need. Multiple functionalities are tailored to meet specific business needs. Logs are essential for any business, and Datadog manages logs effectively. Rum sessions are something new to me and have given us a new perspective on how to reverse engineer issues that we see for our customers.
1. It is well suited when you need to monitor large scale of metrics as compared to Prometheus it is faster,more reliable and can provide you metric for more retention period. 2. Uses less resource to run application , can easily be containerised 3. It supports both push and pull models and can be intergated with multiple alerting systems
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
Datadog's user interface is quite friendly and easy to navigate. With menus clearly categorized, and ability to bookmark important dashboards, one can easily find what they're looking for. For dashboards, ability to move and resize visualizations and group them, is really helpful to organize dashboards. Automatic suggestions from Datadog for important visualizations based on the metrics and logs would provide another level of ease of use.
The support team usually gets it right. We did have a rather complicate issue setting up monitoring on a domain controller. However, they are usually responsive and helpful over chat. The downside would be I don’t think they have any phone support. If that is important to you this might not be a good fit.
I selected Datadog because of its features and the wide range of integration support. As I already told it supports more that 600+ integrations which helps and organization to keep everything in a single place and also its AI feature which is reducing the time for root cause analysis. Its custom dashboards features which helps us to visualize the data in a more attractive way.
Victoria metrics is cheaper and more efficient than Prometheus, in terms of data ingestions, hardware resources, and Storage mechanism, also supports Prometheus extensions, and query language by default. Although Prometheus has a larger community and support, because of the interoperability of Victoria metrics the difference wouldn't concern us much. At the same time, it made our migration simpler