Skip to content

Error handling for ENOTFOUND #8

@br0p0p

Description

@br0p0p

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.

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