You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Promtail is now configured with the docker pipeline stage, and produces errors:
level=info ts=2021-02-28T21:17:33.936395393Z caller=tailer.go:125 component=tailer msg="tail routine: started" path=/var/log/kern.log
ts=2021-02-28T21:17:33.936462167Z caller=log.go:124 component=tailer level=info msg="Seeked /var/log/kern.log - &{Offset:0 Whence:0}"
level=debug ts=2021-02-28T21:17:33.936771177Z caller=json.go:130 component=file_pipeline component=stage type=json msg="failed to unmarshal log line" err="ReadMapCB: expect { or n, but found F, error found in #1 byte of ...|Feb 28 09:0|..., bigger context ...|Feb 28 09:03:30 grafrican kernel: [570410.390357] d|..."
level=debug ts=2021-02-28T21:17:33.936845072Z caller=json.go:130 component=file_pipeline component=stage type=json msg="failed to unmarshal log line" err="ReadMapCB: expect { or n, but found F, error found in #1 byte of ...|Feb 28 09:0|..., bigger context ...|Feb 28 09:03:30 grafrican kernel: [570410.390359] d|..."
level=debug ts=2021-02-28T21:17:33.93690619Z caller=timestamp.go:176 component=file_pipeline msg="extracted data did not contain a timestamp"
level=debug ts=2021-02-28T21:17:33.9368872Z caller=json.go:130 component=file_pipeline component=stage type=json msg="failed to unmarshal log line" err="ReadMapCB: expect { or n, but found F, error found in #1 byte of ...|Feb 28 09:0|..., bigger context ...|Feb 28 09:03:30 grafrican kernel: [570410.390803] d|..."
This is consistent with processing of a docker stage:
Expected behavior
Logs to be processed with no pipeline stages, i.e. the scrape_configs entry should behave as if it were provided pipeline_stages: [].
Environment:
Irrelevant.
Screenshots, Promtail config, or terminal output
See above
The text was updated successfully, but these errors were encountered:
Describe the bug
When defining a
scrape_configs
entry, if thepipeline_stages
key is omitted then adocker
pipeline stage will be created by default.The definition can be found here:
To Reproduce
Steps to reproduce the behavior:
HEAD
)HEAD
) with config:Promtail is now configured with the
docker
pipeline stage, and produces errors:This is consistent with processing of a
docker
stage:Expected behavior
Logs to be processed with no pipeline stages, i.e. the
scrape_configs
entry should behave as if it were providedpipeline_stages: []
.Environment:
Irrelevant.
Screenshots, Promtail config, or terminal output
See above
The text was updated successfully, but these errors were encountered: