Skip to content

Oversize messages are causing a silent failure of the application #59

@MarcoVigna17

Description

@MarcoVigna17

Basically, what the title says...

In my application I'm using

    "winston": "^3.2.1",
    "winston-transport": "^4.3.0"

and I noticed that logging messages bigger than the UDP max allowed size (65535 bytes) causes an error that won't be reported, but that makes my application silently fails.

Looking on the web, I found this PR for winston-syslog that is describing (and fixing) the same problem: winstonjs/winston-syslog#123

Just wondering, how it's possible to fix the same thing in winston-transport?

Or is it possible to use winston-transport along with winston-syslog without refactoring m application?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions