8b454dd79e
This defines a 'context' object that is passed to each API handler. Right now the context just has a unique 'requestID' for each API call. The next steps would be: - use this 'requestID' in our logging. - determine the best way to format the logging to include this info. In particular for log events that generate multiple entries in the log we can use the requestID to help correlate the log entries. Adding the requestID to the logging will be a challenge since it could mean changing every single logrus.XXX() call to pass in the 'context' object. But first step is to agree on a format, which we can discus in a subsequent PR, but my initial thoughts are to add it right after the timestamp: current format: INFO[0039] POST /v1.21/build?buildargs=%7B%22foo%22%3A%22xxx%22%7D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&memory=0&memswap=0&rm=1&t=&ulimits=null proposed format: INFO[0039-83dea1222191] POST /v1.21/build?buildargs=%7B%22foo%22%3A%22xxx%22%7D&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=Dockerfile&memory=0&memswap=0&rm=1&t=&ulimits=null Signed-off-by: Doug Davis <dug@us.ibm.com> |
||
|---|---|---|
| .. | ||
| client | ||
| fixtures | ||
| server | ||
| types | ||
| common.go | ||
| common_test.go | ||
| README.md | ||
This directory contains code pertaining to the Docker API:
-
Used by the docker client when communicating with the docker daemon
-
Used by third party tools wishing to interface with the docker daemon