Jaime Fullaondo

Unfortunately we didn't find the time to get this done for `5.9.0`, so pushing up to `5.10.0`, thank you for the patience.

Hey @dballing, thank you for taking the time to look into this. The requirement for `mysql>=5.6` isn't completely arbitrary :) it was done because the check doesn't officially support EOL'd...

Hi All! Once again thank you @prudhvi and @SerCeMan for your feedback. We have started a bit of a revamp to improve client performance - first focusing on throughput (though...

@prudhvi @AndrooHan we have released `v2.10.0` with a large set of improvements, and a bunch of new knobs we can use to improve performance. We have also been able to...

@kao73 unfortunately the client does not currently behave in this way. Upon a call to `close()` the agent shuts down its workers and client submitted metrics that have not yet...

We have merged and released https://github.com/DataDog/java-dogstatsd-client/pull/105 to reduce the number of allocations, we now rely on StringBuilders differently to achieve this. We can probably do even better, and your suggestion...

@ayeletmorris I'm not sure how we can help you, `micrometer-registry-statsd` does not use this project, `java-dogstatsd-client`, internally. Perhaps I'm misunderstanding your question?

It's probably this: https://github.com/DataDog/dogstatsd-csharp-client/issues/64

Please note that this was partially addressed here: https://github.com/DataDog/datadog-agent/pull/4129; the solution doesn't flush open dogstatsd time buckets, but it would flush everything else: - closed time buckets. - check metrics.

note: I can see the tests failing until we actually release the new JMXFetch version.