Skip to content

Improve logging when autodiscover configs fail #20568

Closed

Description

When using autodiscover with Filebeat, errors like the following occur:

ERROR [autodiscover] autodiscover/autodiscover.go:209 Auto discover config check failed for config '{
"docker-json": {
"cri_flags": true,
"format": "auto",
"partial": true,
"stream": "all"
},
"json": {
"add_error_key": true,
"keys_under_root": true,
"overwrite_keys": true
},
"symlinks": true,
"type": "container"
}', won't start runner: each input must have at least one path defined

This kind of errors can be considered as non-fatal since they came from Pod events introduced at https://github.com/elastic/beats/pull/18979/files#diff-3a3ae93d44b91ab240d462f8f7eddc2cR365.

However we should avoid logging them since it can be confusing when looking at the logs for actual errors.

Related to #11834 (comment).

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

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions