Skip to content

TCP, UDP and probably more inputs should allow parsers #11688

@OlafTitz

Description

@OlafTitz

Is your feature request related to a problem? Please describe.
I tried to replace a Tail input with a setup utilizing the UDP input (#11687) and found that this input does not allow to set a parser (contrary to the documentation which suggests that all inputs may involve a parser).

Describe the solution you'd like
Allow parsers on all inputs, at least all which take free-form input like TCP, UDP, Blob(?), Head.

Describe alternatives you've considered
A Regex parser can be replaced by a Content modifier processor but that is less powerful, see #11689.

Additional context
As it stands now, it is not possible to simply replace an input which reads a file (Tail) with one which reads from a socket (TCP/UDP) without redesigning the whole pipeline.

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