Skip to content

match fails after encountering binary text within file #187

@kuro-obi

Description

@kuro-obi

Hello there
I encountered a case where grok_exporter would not match further instances if the matching line occurs after some binary/hex characters. Of course one way to circumvent this is if I have the input as stdin, and simply use tail -f file.log | grep -a pattern.

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