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.
M.E.L.I.G.: From VM to Unikernel and SOA to Serverless
During the latest MeetUp we talked about the rise of virtualization techniques and how software changed from clunky big services to state-less functions.
Docker 1.13 qwatch log/events handler
Last week-end I was hacking on my metrics collector to be able to fetch docker-engine and docker-container stats.
But as my MeetUp in Berlin is called M.E.L.I.G. (Metrics,Events,Logs,Inventory and Glue), there is much more to it then metrics.
This week-end I hacked on a new tool: qwatch
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
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. :)
GOCD + metric stacks via Docker Services
I won't apologise for the log delay between posts again, busy times...
But that should discourage you from checking in every once in a while - I got something nice today, at least I think so. :)
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.
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... :)
MELIG-1 M: State of InfluxDB
Today was the first instance of a M.E.L.I.G. MeetUp. The topic was about metrics in general (broad general) and what the new version of InfluxDB is going to introduce; mainly in terms of the storage backend.
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...
WrapUp NeIC2015 - seeds planted
Yesterday the Nordic e-Infrastructure Collaboration Conference (NeIC2015) came to an end.
I talked about QNIBTerminal and what I am working on; connecting dots between metrics (graphite-ecosystem), logs (logstash & friends), inventory (QNIBInventory based on a GraphDB) and SLURM (cluster resource scheduler). I put it up on youtube: