4 ms·
What do you use for log aggregation and monitoring/metrics? And how do you deploy new versions with zero downtime? And how do you manage kernel/OS upgrades?
by ngrilly 8y ago
What do you use for log aggregation and monitoring/metrics? And how do you deploy new versions with zero downtime? And how do you manage kernel/OS upgrades?
- gerbilly 8y ago> log aggregation Graylog, with applications using various GELF libraries to send logs to it. > metrics graphite/grafana > And how do you deploy new versions with zero downtime? I don't deploy with zero downtime, but within say ~5min. This is acceptable to us. We use jenkins with a lot of tests to ensure components are in good shape, then we mostly manually deploy them, but with a script. Sometimes we deploy directly from jenkins. > Kernel os upgrades All our stuff is internally hosted, so we handle those infrequently. This stuff isn't exposed the the open internet, so we upgrade when we get around to it, or when we encounter a bug.
- ngrilly 8y agoThanks for following up! I'm not surprised because I noticed on HN and in other online discussions that almost all the people that advocate against Kubernetes and PaaS (Heroku, App Engine, Clever Cloud, Scalingo, etc.) are willing to tolerate downtime during deploys and during OS upgrades.
- gerbilly 8y ago> are willing to tolerate downtime during deploys and during OS upgrades. Yeah, that's not a big deal for us. We don't have customers, and this environment is for internal use at the company. You could say it's a 'semi production' environment.
- ngrilly 8y agoI like the "semi-production" concept :-)
- therealdrag0 8y agoDeploying with zero down time with Ansible is kinda the same as it's always been: - Deploy to one host - Wait for health checks to pass - Deploy to second host. Load balancer takes care of the rest.