Skip to content

Don't mute/discard connection when "quick listener check" fails #6

@zstyblik

Description

@zstyblik

Hello,

I'm wondering whether it would be possible to try to either connect(un-mute) or from time to time.

Currently, when:

Failed to init StatsD: write udp [::1]:51628->[::1]:8125: write: connection refusedSlept: 0

Then no attempt is made to connect again. I don't want to fail application just because connection cannot be established, although may be I should. Also, it seems to me a bit cumbersome to introduce some check-whether-StatsD-is-initialized logic.

Would it be possible to try to connect from time to time eg. on flush() or just from time to time and un-mute?

If I kill listener, then connection is re-established once listener comes back. However, if listener isn't there when StatsD client is initialized, we never try again.

Thanks,
Z.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions