3 ms·
Their billing is HORRIBLE. Its actually a big reason why we are investigating moving off. Its insanely unclear. I get that their product domain is complex, and
by 013a 7y ago
Their billing is HORRIBLE. Its actually a big reason why we are investigating moving off.
Its insanely unclear. I get that their product domain is complex, and thus its hard to bill for, but... its things like, if you're container-focused, you still pay for nodes, and you get X number of containers per node that you're allowed to track. You wire up an AWS integration and it (1) counts as a node? I've heard different things from different salespeople about this, and (2) drives up your AWS bill like crazy because of the amount of data it pulls (our AWS bill is low-five-figures, and the Datadog integration represents 3-5% of it). The datadog-agent inside our kube clusters was constantly one of our largest logging services, until we started filtering those out. We had one of our services go crazy on logs one month, driving up our bill by 1500% until someone caught it (we're small. we make mistakes. we're learning). You can't delete the logs, they wouldn't, so we had to eat a 5 figure bill when we're used to, like $1000/month.
And its expensive. Maybe its comparable to something like New Relic, I don't know, but relative to StackDriver or CloudWatch? Its in a totally different league. Just on logging, its hard to do apples-to-apples because DD bills on lines whereas CloudWatch bills on bytes, but for our logging patterns, even with our annual enterprise discount on DD (and no discounts on AWS) DataDog is about 5x more expensive. CloudWatch (even with the new Insights product) is pretty hard to ask front-line developers to use, but StackDriver is pretty nice, and its also pretty cheap.
We joke about Datadog among our ops team. When we were investigating adopting them, I signed up for an account with my company email. Within a week, members of their sales teams were emailing our frontend developers, who I imagine they found by linking my company email to a LinkedIn company, about setting up a call. I'd get about one unprompted call a week from someone from their sales org.
Their product is great. Possibly even special, though I don't believe its miles better than StackDriver. The company is a nightmare. I tell everyone I can to stay away, at least until they sort out their sales and technical support organizations, if they ever do.
- stingraycharles 7y ago“And its expensive. Maybe its comparable to something like New Relic, I don't know, but relative to StackDriver or CloudWatch? Its in a totally different league. ” To be fair to Datadog, their UI/UX is also in a totally different league. Stackdriver Logging is a total PITA to use when trying to investigate and correlate historical logs.
- Karunamon 7y ago>We joke about Datadog among our ops team. When we were investigating adopting them, I signed up for an account with my company email. The exact same thing happened to me an employer or two ago. Their sales droids were so aggressive with the calls (one time, many of our people were on vacation, one guy answered, told them no thanks, and then that same caller proceeded to ring nearly every phone in the cube farm sequentially) that, to this day, that team refers to getting bothered by pushy vendors as "getting datadogged".
- nrmitchi 7y ago> The datadog-agent inside our kube clusters was constantly one of our largest logging services This. Just this. Until I recognized this, these agent logs were making up more than 50% of our total log volume. These were, for the most part, a single log message that an APM was malformed. I only noticed this when renewing my companies Datadog contract, and couldn't fathom how we had been generating so many logs. I was pretty disappointed when their sales rep had been pushing us to increase our committed log volume, without mentioning that literally thousands of dollars per month was being spent for Datadog to send themselves their own logs. As far as I'm concerned these logs should either be filtered out of the index by default, or not count towards billing.