Flushing the same metric multiple times in the same second overwrites previous values

[scmorse]

If you increment a counter, flush the message, and then before the UTC timestamp has rolled into the next second, increment the same counter with the same tags (and flush again), only one of your two increments will show up in datadog. I think Datadog has some de-duplication / unique indexing that only tracks a unique metric per second. I think this library would need to keep in-memory up to 1 second of messages, to be able to track and send the right stats.

[eeubank]

@scmorse we were seeing that same issue with this library. Since it seems to have been abandoned we've switched to datadog-lambda-js and have had better results.

[Mr0grog]

I just finished a PR that adds distribution metrics, which won’t have this problem (datadog-lambda-js only sends distributions, which is how it works around this issue). If the core issue here is still causing you problems and doesn’t get addressed before the next release, you might try using a distribution instead.