Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Error handling for ENOTFOUND #8

Open
br0p0p opened this issue Jun 4, 2019 · 0 comments
Open

Error handling for ENOTFOUND #8

br0p0p opened this issue Jun 4, 2019 · 0 comments

Comments

@br0p0p
Copy link

br0p0p commented Jun 4, 2019

Right now I'm having to check if the hostname exists with dns.lookup before I add the transport because there's no well defined way to handle connection issues when creating the transport. It would be greatly beneficial to, for instance, catch the ENOTFOUND error from the new LogstashTransport(...) call.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@br0p0p