4 ms·
You're of course right. But also, are you shipping all the logs? Of course you're shipping application logs somewhere searchable, what about gc logs, syslog, k
by tasuki 4y ago
You're of course right.
But also, are you shipping all the logs? Of course you're shipping application logs somewhere searchable, what about gc logs, syslog, kernel logs, etc? Is it never necessary to run ad hoc commands on your production systems?
- amtamt 4y agoHow are gc/ syslog/ kernel logs are special and not sent to central logging? Ad-hoc logs (such as thread dumps etc.) can also be triggered via safe application end points from restricted locations. > "Is it never necessary to run ad hoc commands on your production systems?" Ad-hoc commands in production AS ROOT should be exception, not norm, and reserved for on-call members, not every developer working on team. Even the most competent people, sysadmin or developer, can make a mistake. I did not say no commands should ever be run on production, there could be non-root read-only accounts. I am opposed to everyone having root on production. I have seen enough data loss incidents or full blown outages because of mistakes.
- tasuki 4y agoWell done you, I guess? Nothing to disagree with. I'm just amazed this can be actual reality :)
- glotzerhotze 4y agoIt takes a while to get there - and a lot of discipline of those involved.
- glotzerhotze 4y agoIn an ideal world, you wouldn‘t need that. But most systems never matured to be considered being in an ideal state / world.