gliderlabs / gliderlabs/logspout
Multiline logging failed to take effect
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4.7k
- Forks
- 661
- PR merge metrics
- No merged PRs in 30d
Description
Judging from the left side of the picture, these log messages are not sent together, **sent line by line**
#### configuration information
```
docker run -d --name="logspout" --volume=/var/run/docker.sock:/var/run/docker.sock \
--volume=/etc/hostname:/etc/host_hostname:ro -p 8000:80 \
-e MULTILINE_PATTERN='^\[\d{4}-\d{2}-\d{2}' \
-e LOGSPOUT=ignore \
-e MULTILINE_MATCH=first \
gliderlabs/logspout \
multiline+syslog+tcp://172.17.0.1:5000
```
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the provided Docker command with the multiline and syslog configuration, then trace the multiline/syslog routing behavior. Done means multiline log messages are sent together rather than line by line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- devops, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100