Walking around the exhibit hall at DockerCon, and then trying to pick sessions, I couldn't help but feel that heading a small engineering team I was at the wrong conference.
Meanwhile, the booths were 50% "we can install Kubernetes for you" and 50% "we can do monitoring/logshipping for your Kubernetes", which is interesting given that the Kubernetes guys are working on solving the first issue and Prometheus/Grafana/Fluentd solve the second issue already.
Fluentd is a terrible log shipper: sub-second timestamping is not yet supported in the stable build, support is patchy in the plugin ecosystem in 0.14. There's also some humdingers buried in the source (Rational numbers for time arithmetic?) Abstractions leak all over the place. The plugin ecosystem is weak and the API shims in the minor version API break are poor and in my experience break semver.
Prometheus has the right idea, but I wouldn't want to be running and scaling my telemetry system if I'd also taken on the burden of running my own container scheduler. Whilst I've no doubt Prometheus can be made to scale, I'd rather somebody else made the federation decisions for me.
Oh well :\
One problem with the Austin convention center is that it's VERY spread out, so it's easy to miss an entire chunk of sessions because they're almost impossibly far if you don't know what you're looking for.
As this thread insinuates, Docker is a VC-driven fad that has been seized upon by posers as the next buzzword to plaster across their resume. I wish more engineering managers were willing to stand up to this nonsense.