Skip to content


M.E.L.I.G.: Log/Event/Metric Collection within Containers

Yesterdays (ok, late post - at the last) MeetUp was first and foremost about the Container Manifesto, which aims to foster understanding about how to build and run a Container.

Afterwards we figured that I missed 'Containers should start fast (thx Lukasz)' as an additional point - next time. :)

For today I will just put the video in here, a separat blog post might follow - even though I feel it is not that necessary, as no code was executed.

Docker 1.13 Prometheus end-point and qcollect

Docker 1.13 is on it's way and I like what comes to light.

The highlights from where I stand are:

  • service port publishing now as mode host or ingress, which allows for service ports to be outside of the IPVS load-balancer and just exposed on the SWARM node.
  • the load-balancer seems to honour established connections
  • experimental has an end-point /metrics, which exposes Prometheus formatted metrics.

And this last bit got me interested. So much, though, that I hacked a Prometheus collector into qcollect. :)

Hello World of qcollect

A while back I stumbled upon Fullerite, a GOLANG metrics collector, which can reuses the collectors of the python Diamond collector.

One of the issues I had was, that it is not using the event time, but the process time of collected metrics. Thus, if you want to bulk update collected metrics, they will all have the same timestamp of the time they are push to the metrics backend.

Hello Sensu

Even though I like Consul a lot (it is the foundation of my stacks in terms of service/node discovery) it's most likely not a replacement for a monitoring framework with notification handlers, distributed checks and a nice dashboard.

I assume that most of the readers have used NAGIOS at some point and decide to hate-love it. It works, but only kinda... :)

qnib/monster - all in one box

OK guys, since the ELK is quite popular on docker-hub, I was wondering if I could push it one notch further. Turns out I could, please welcome qnib/monster...

git (master) $ git clone
git (master) $ cd docker-monster
docker-monster (master) $ docker-compose up -d
Creating dockermonster_monster_1...
docker-monster (master) $