Core_interceptor
can be used to handle core dumps in a dockerized
environment.
It listens on the local docker daemon socket for events. When it receives a
die
event it checks if the dead container produced any core dump or java
heap dump. Then the container is committed as IMAGE_NAME:TAG
:
IMAGE_NAME
is composed by the name and tag (if any) of the dead container source image separated by "_".TAG
is composed by the first 12 characters of the dead container ID
The resulting image is then pushed to a configurable Docker registry, and deleted from the local node. Finally a notification can be sent to a Kafka cluster or to a REST endpoint.
The notification content is:
{version:1.0, timestamp: now ,pushed: PUSHED, name: IMAGE_NAME, tag: TAG, hostname: HOST, object: OBJECT}
PUSHED
is a flag telling if the creation/push of the image succeedHOST
is the name of the machine where the container was runningOBJECT
is the type of object produced, e.g.,core
The notification is posted to the topic cores
.
You may optionally provide an HTTP URI: the core interceptor will perform a POST to the given URI. The body of the request will be the same context as in the Kafka notification.
To run this program you need:
- a running docker deamon
- write access to the docker socket
- access to a docker registry with rights to push images (optional)
- write access to a Kafka cluster (optional)
To build this program you need:
- golang compiler
- go tools
go build
The program should be run by a user with the rights to access to the docker socket (e.g., root)
./core_interceptor -h
The logging is configurable via command line and uses the glog package. Core interceptor errors are always logged to the system journal. You can get them by running
journalctl _COMM=core_intercepto
##Licence