You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that Flush() will flush some data, but won't flush stats. This is causing issues in the parametric tests. We should investigate if there's a good reason for this on the Go tracer side, or if this is just a bug.
The text was updated successfully, but these errors were encountered:
Flush() flushed buffered traces, but it did not flush stats. We enabled flushing stats by adding a flush method to the statsdClient interface and calling that method when trace flushing occurred.
Fixes#1547
* ddtrace/tracer: enable stats flushing when Flush() is called
Flush() flushed buffered traces, but it did not flush stats. We enabled flushing stats by adding a flush method to the statsdClient interface and calling that method when trace flushing occurred.
Fixes#1547
* ddtrace/tracer: add unit test for flushing stats
Altered TestFlush to verify that flushSync() flushes stats
* ddtrace/tracer: changed add-assign to increment operator
* ddtrace/tracer: added flushing for stats concentrator and test for flushing stats concentrator
* Change assert from Equal to Zero
Co-authored-by: Katie Hockman <katie@hockman.dev>
* Change bucketSize of concentrator in TestFlush to defaultStatsBucketSize
Co-authored-by: Katie Hockman <katie@hockman.dev>
* changed start time for span in TestFlush to use defaultStatsBucketSize
* Fixed flipped assertion for statsdclient flush unit test
Co-authored-by: Andrew Glaude <andrew.glaude@datadoghq.com>
* flush current bucket on call to flushAndSend
Co-authored-by: Katie Hockman <katie@hockman.dev>
Co-authored-by: Andrew Glaude <andrew.glaude@datadoghq.com>
See DataDog/system-tests#596 for more context.
It appears that
Flush()
will flush some data, but won't flush stats. This is causing issues in the parametric tests. We should investigate if there's a good reason for this on the Go tracer side, or if this is just a bug.The text was updated successfully, but these errors were encountered: