4 ms·
It's really easy to run up a huge bill from Datadog if, for example, some engineer adds a whole lot of new tags/dimensions to metrics data because they think it
by vosper 4y ago
It's really easy to run up a huge bill from Datadog if, for example, some engineer adds a whole lot of new tags/dimensions to metrics data because they think it would be useful to have in the future (full disclosure: that was me, in a previous role. I think I "spent" almost $30k on extra metrics before anyone realised and we tracked down what happened - I was new to DD and didn't even know they charged extra for those things)
- api 4y agoWhat was the size of this data set? Curious as to just how much data you have to handle to incur a bill like that.
- thayne 4y agoThey charge based on the number of unique combinations of metrics and tags. So if you were to add a tag for something with high cardinality, like say the source ip address, or even a browser user agent, you can ring up a pretty high bill without even sending that much data, because you have a large number of metrics.
- vosper 4y agoThis is pretty much what happened, but in my case it was a bunch of IDs for objects owned by customers. It was intended (and did) to provide detailed performance metrics related to our Elasticsearch searches, but in the end I had to drop a lot of them due to cost.