Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filebeat autodiscover hints fail to create inputs #12346

Closed
jsoriano opened this issue May 29, 2019 · 0 comments · Fixed by #12348
Closed

Filebeat autodiscover hints fail to create inputs #12346

jsoriano opened this issue May 29, 2019 · 0 comments · Fixed by #12348
Assignees
Labels
blocker bug containers Related to containers use case Filebeat Filebeat Team:Integrations Label for the Integrations team v7.2.0

Comments

@jsoriano
Copy link
Member

jsoriano commented May 29, 2019

Filebeat autodiscover hints don't create valid inputs on 7.2 branch, possibly related to #12162 and/or #12272.

For confirmed bugs, please report:

  • Version: 7.2 branch
  • Operating System: Linux
  • Steps to Reproduce: Use filebeat with hints-based autodiscover

This error appears continuously in filebeat log:

2019-05-29T15:40:46.071Z	ERROR	[autodiscover]	cfgfile/list.go:96	Error creating runner from config: each input must have at least one path defined

Tested configuration:

    filebeat.autodiscover:
      providers:
        - type: kubernetes
          hints.enabled: true

There is a workaround with the new possibility of adding a different default config (#12272), this works:

    filebeat.autodiscover:
      providers:
        - type: kubernetes
          hints.enabled: true
          hints.default_config:
            type: container
            paths:
              - /var/log/containers/*${data.container.id}.log
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocker bug containers Related to containers use case Filebeat Filebeat Team:Integrations Label for the Integrations team v7.2.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants