Skip to content

[maintained fork] Arbitrary stream support, relative gauges, fixes, etc #40

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 39 commits into
base: master
Choose a base branch
from

Conversation

joeycumines
Copy link

@joeycumines joeycumines commented Feb 14, 2020

I have created a fork of this repository and intend to maintain it, but I figured I may as well make a PR for visibility, even though this project seems to be dead.
I have avoided any breaking changes (AFAIK), and have unit tested the new features I have added. Test coverage is still at 100%.

As far as I know, mine is the only backwards compatible fork. All that I've seen seem to merge some variation of #7. I've added an option to disable the initial UDP check / ping, but it's still default behavior.

I am no longer the only contributor to my fork, and the change list has grown, so please take a look at https://github.com/joeycumines/statsd/blob/master/README.md .

stevenh and others added 30 commits January 30, 2017 17:11
Telegraf doesn't support support negative counters, requiring relative gauge values instead. This adds the new method GaugeRelative to allow for this.
Add GaugeRelative to support Telegraf statsd implementation
Please refer to https://github.com/gdiazlo/statsd as a solution to this issue in the original repo alexcesaro#6.

This will add the functionality needed while keeping the additional changes that are currently present in this fork.

It is useful to have this change as the metrics within a service *shouldn't* stop a service from operating. Currently, it works as is but as soon as `.Clone` is called on the client, it crashes due to a nil conn (caused by this check).
Update client to not require a successful ping
Close relative gauges which was creating corrupt statsd protocol.

Also:
* Remove TestUDPNotListening which is broken since a51b81.
* Fix lint warnings.
* Enabled lint checks in travis.
* Enabled 1.x and master only for travis as older versions fail to
  detect go mod support properly.
This implementation does not provide connection state management. Handling
connection failures and retrying as necessary should be implemented by the
caller, if desired.
(fix 2/2 for alexcesaro#6)

Adds an option to facilitate initialising an unmuted client for UDP conns
where the server is unreachable.
Merges 'multiplay/master', with unnecessary and duplicated changes removed.
Fixes and better testing to come.
Also fixes handling of -0.0 within Gauge, by stripping the sign.
This is a follow up fix for alexcesaro#12.
@joeycumines joeycumines changed the title Arbitrary stream support and related fixes (inc. TCP fixes) Arbitrary stream support, relative gauges, multiple fixes Jan 1, 2022
@joeycumines joeycumines changed the title Arbitrary stream support, relative gauges, multiple fixes [maintained fork] Arbitrary stream support, relative gauges, multiple fixes Jan 1, 2022
@joeycumines joeycumines changed the title [maintained fork] Arbitrary stream support, relative gauges, multiple fixes [maintained fork] Arbitrary stream support, relative gauges, fixes, etc Jan 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants