Skip to content

Filebeat should start even when all input files are inaccessable. #582

Closed
@C0RD

Description

@C0RD

Hello,

I would like to have a switch to keep filebeat running even if all input-files are inaccessable.

Currently filebeat checks for those inputfiles and if it can't open them, it stops with "No paths given. What files do you want me to watch?". But I have files configured, but they are not there yet (or due to permissions not readable for filebeat.)

This is needed, as the logfiles i want to track aren't there when deployment and start of filebeat happens. Filebeat should just start (maybe complain in it's Logfile) and wait for those Logfile become available.

Thank you,
Cord

PS: WOuld be nice if you could set the old Repository (and the issue-Tracker) at https://github.com/elastic/filebeat read-only or make the move more prominent there.

Activity

C0RD

C0RD commented on Dec 22, 2015

@C0RD
Author

I found an error in the configfile, which caused this. will open a new issue for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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

        Participants

        @C0RD

        Issue actions

          Filebeat should start even when all input files are inaccessable. · Issue #582 · elastic/beats