Release 9.1.0#228
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f265e42c4c
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| ## Changes | ||
|
|
||
| * [FEATURE] Add synchronous mode for serverless environments. Set `StatsdConfig.SynchronousMode = true` to bypass the async background worker and send metrics directly on the calling thread, eliminating metric loss on sandbox freeze in AWS Lambda and similar runtimes. See [#227][]. |
There was a problem hiding this comment.
Document the required Flush call for synchronous mode
When users enable this in a serverless handler and emit only a small batch of metrics, StatsdConfig.SynchronousMode = true does not by itself send every metric immediately: the builder still keeps the default client-side aggregators and SynchronousSender.Send only routes into BufferBuilder, so data stays buffered until Flush() (or a full packet) forces it out. The existing API docs mention calling Flush() at the end of each invocation, but this release note says setting the flag alone eliminates sandbox-freeze loss, which can lead Lambda users to drop metrics on freeze.
Useful? React with 👍 / 👎.
| <PackageId>DogStatsD-CSharp-Client</PackageId> | ||
| <TargetFrameworks>net461;netstandard2.0;netcoreapp3.1;net6.0</TargetFrameworks> | ||
| <LangVersion>latest</LangVersion> | ||
| <PackageVersion>9.1.0</PackageVersion> |
| [#209]: https://github.com/DataDog/dogstatsd-csharp-client/issues/209 | ||
| [#211]: https://github.com/DataDog/dogstatsd-csharp-client/issues/211 | ||
| [#213]: https://github.com/DataDog/dogstatsd-csharp-client/issues/213 |
There was a problem hiding this comment.
Are these just commits that were missing from other change log entries?
There was a problem hiding this comment.
Yes, they are from 9.0.0.
Largely following the release process outlined [here](https://datadoghq.atlassian.net/wiki/spaces/AM/pages/2523399106/DogStatsD-CSharp-Client) add a couple of skills. 1. prepare the release (#228 is the first example of this) 2. push the new release to nuget
Release 9.1.0
Changelog and version bump for the 9.1.0 NuGet release.
Checklist
Once merged, run
/publish-releaseto tag, build, and push to NuGet.