Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/timstott/docker-log-drivers-adventures
Adventures with Docker log drivers
https://github.com/timstott/docker-log-drivers-adventures
Last synced: about 1 month ago
JSON representation
Adventures with Docker log drivers
- Host: GitHub
- URL: https://github.com/timstott/docker-log-drivers-adventures
- Owner: timstott
- Created: 2015-08-18T17:10:37.000Z (over 9 years ago)
- Default Branch: master
- Last Pushed: 2015-10-09T11:02:30.000Z (about 9 years ago)
- Last Synced: 2024-04-14T20:32:19.126Z (9 months ago)
- Language: Ruby
- Homepage:
- Size: 484 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Adventures with Docker log drivers
Evaluate native Docker log driver integration with GrayLog.
## Prerequisite
- Docker 1.8
- `docker.local` host points to your docker host
In the following exmaples logs are generated by a dummy Sinatra application.
Build the dummy application with `docker build -t sinatra_docker ./sinatra`
Generate logs by making requests `curl http://docker.local:9292`
## GELF Output
Docker formats logs in GELF and sends them to GrayLog over UDP.
To view the output in GrayLog start a GrayLog instance with a GELF UDP input.
```
docker run -i -t -p 9229:9292 --log-driver=gelf --log-opt gelf-address=udp://docker.local:12201 sinatra_docker
```
### Sample Output
### Observations
Docker wraps the message outputed by the application in a new GELF message. The original message becomes a String.
GrayLog provides `Extractors` to extract data from any text message. It is tedious to work with when messages attributes are variable.
Messages with length over 30k were sent without problems.
## Fluentd Output
View the output in fluentd with `docker-compose up`
```
docker run -i -t -p 9292:9292 --log-driver=fluentd --log-opt fluentd-address=docker.local:24224 sinatra_docker
```
### Observations
Similarly to the GELF log driver, Docker wraps the message outputed by the application.
The log driver then forwards the logs to a fluentd agent.
There custom formatters and outputs can be added to the fluentd agent to extract the application message.
As oposed to GrayLog `Extractors` fluentd formatters are more flexible to parse and format messages.
The fluentd log driver send logs to the agent over TCP. Preliminary observations revealed the log driver does not reconnect to the agen when the connection breaks.
This needs further investigation.
## ~~docker-compose~~
The lastest version does not provide support for fluentd and gelf log drivers (docker/compose#1878).
- docker-compose > 1.4
- `docker.local` points to your docker host