Re:I usually run 'w' first when troubleshooting unknown mach...
by closeparen on Tuesday March 27, 2018 @02:54AM
(#16685942)
Our containers are immutable, but the bare metal hosts they run on aren’t.
[ Parent
| on HN ]
Re:I usually run 'w' first when troubleshooting unknown mach...
by movedx on Tuesday March 27, 2018 @04:13AM
(#16686360)
No, but the "bare metal hosts" should be configured through configuration management and all logs sent "off site". I've been in the same boat and never had to log into a bare metal box. K8s and Ansible will do that for ya.
Re:I usually run 'w' first when troubleshooting unknown mach...
by freehunter on Tuesday March 27, 2018 @12:05PM
(#16689818)
I work on those "off site" machines that collect your logs and I'm sitting on one as root right now.
Ansible doesn't get you everywhere.
Re:I usually run 'w' first when troubleshooting unknown mach...
by movedx on Wednesday March 28, 2018 @12:57AM
(#16695395)
Yikes! We use time series databases, so we simply export the data from them to analytical software or our local machines.
InfluxDB is a simple command to extract what I need and then work with it from there.
Re:I usually run 'w' first when troubleshooting unknown mach...
by closeparen on Tuesday March 27, 2018 @12:10PM
(#16689875)
Puppet deploys a variety of host-level agents like L7 routing, dynamic config updaters, the scheduler agent (of course), metrics, logging, and tracing collection. Usually they work, but it’s necessary more often than you’d think to find out why one has fallen over and fix it, and to run diagnostic tools to investigate performance anomalies.