Bump dogstatsd-ruby from 4.8.3 to 5.3.3

[dependabot]

Bumps dogstatsd-ruby from 4.8.3 to 5.3.3.

Release notes

Sourced from dogstatsd-ruby's releases.

v5.3.3

5.3.3 / 2022.02.02

• [IMPROVEMENT] Add option "buffer_flush_interval" to flush buffered metrics #231[] by [@​abicky][]

• [IMPROVEMENT] Add Sender.queue_size limits to limit number of buffered metrics #232[] by [@​djmitche][]

• [IMPROVEMENT] The client can now be configured to use UDS via the DD_DOGSTATSD_SOCKET environment variable. This variable does not take precedence over any explicit parameters passed to the Statsd constructor. #227[] by [@​djmitche][]

Changelog

Sourced from dogstatsd-ruby's changelog.

5.3.3 / 2022.02.02

• [IMPROVEMENT] Add option "buffer_flush_interval" to flush buffered metrics #231[] by [@​abicky][]

• [IMPROVEMENT] Add Sender.queue_size limits to limit number of buffered metrics #232[] by [@​djmitche][]

• [IMPROVEMENT] The client can now be configured to use UDS via the DD_DOGSTATSD_SOCKET environment variable.

master This variable does not take precedence over any explicit parameters passed to the Statsd constructor. #227[] by [@​djmitche][]

5.3.2 / 2021.11.03

• [OTHER] add a warning message for the v5.x update on install #222[] by [@​djmitche][]

5.3.1 / 2021.10.21

• [OTHER] restore connection opening behavior from before 5.3.0 (connections not opened on client instantiation but on the first write instead) #214[] by [@​remeh][]

5.3.0 / 2021.10.06

• [ENHANCEMENT] Automatically re-allocate resources (e.g. background thread) if dogstatsd-ruby is used in an application using forks #205[] by [@​remeh][]

  This will help in scenarios where applications are not handling cleanup/re-creation of the dogstatsd-ruby instances in forked processes. If you are an user of v4.x versions of dogstatsd-ruby and want to migrate to v5.x, please make sure to go through this section of the README and through the migration guide.

• [BUGFIX] Fix client telemetry in applications using forks #205[] by [@​remeh][]

Please note that this version will emit a deprecation message if you are using ruby < 2.1: we plan to drop support for ruby 2.0 in a future minor release.

5.2.0 / 2021.07.01

• [FEATURE] Add single_thread mode for users having issues with the companion thread. #194[] by [@​remeh][]

You can use this mode to avoid spawning a companion thread while using v5.x versions:

# Import the library
require 'datadog/statsd'
Create a DogStatsD client instance.
statsd = Datadog::Statsd.new('localhost', 8125, single_thread: true)
...
release resources used by the client instance and flush last metrics
statsd.close()

Note that if you want to restore the behavior of v4.x versions, you can also configure the buffer to flush on every metric submission:

</tr></table> 

... (truncated)

Commits

• 5d8e7f0 v5.3.3
• 83c0fbc Merge pull request #230 from DataDog/dustin.mitchell/ac-1321
• a528562 Simplify allocation test
• 1cb07a6 Use a constant for the default queue_size value
• e51929b Merge branch 'master' into dustin.mitchell/ac-1321
• 23f73df Merge pull request #232 from DataDog/remeh/fix-tests
• 30770cf specs: a :flush can be triggered.
• 7d752c8 specs: delay in the timer_spec seems to be too short for slow configuration.
• 73e7b52 specs: typo in the forwarder_spec specs.
• c21c445 Merge pull request #231 from abicky/reimplement-buffer-flush-interval
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #22.