3 ms·
Same at CloudNativeCon by the way. I went to the technical-sounding talks (as opposed to "success stories"), but most of them were just "observe as I upload a Y
by majewsky 10y ago
Same at CloudNativeCon by the way. I went to the technical-sounding talks (as opposed to "success stories"), but most of them were just "observe as I upload a YAML file into Kubernetes and stuff happens".
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.
- opsunit 10y ago2c from my experience. 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.