5 ms·
I’ve personally never needed to ssh into my “cattle” even when I could (EC2 instances in an autoscaling group, Docker containers run with Fargate) and I haven’t
by scarface74 7y ago
I’ve personally never needed to ssh into my “cattle” even when I could (EC2 instances in an autoscaling group, Docker containers run with Fargate) and I haven’t missed it when I couldn’t (lambda). For Fargate/Lambda all console output goes to CloudWatch, for EC2 tasks (legacy Windows), we use Serilog with a CloudWatch sink.
But more generically, if you have to log into your cattle for troubleshooting, you probably need a better logging infrastructure.
Then again, if you are referring to how to initially install software, wouldn’t you usually just create an image for it to run?
- tofflos 7y agoIt's for initial installation. I use it to figure out what the image and orchestration settings should be. Packaging an application for containers and container orchestration takes me many, many, attempts to get right. Personally I'm unable to divine the correct combination of settings by reading documentation alone so I try something, enter the container, and look at the outcome.
- xorcist 7y agoIt's nice to have ptrace once in a while.
- scarface74 7y agoThe only time I can think of where copious logging wasn’t good enough for “remote debugging” is when I was writing C code trying to figure out why I was killing the call stack or overwriting memory.
- xorcist 7y agoHaving metrics and logging is a requirement to find out that there is a problem, but it doesn't help much to find out what the problem is.
- scarface74 7y agoIt depends on the granularity of logging. What can local debugging tell you that copious logging at the “debug” level can’t?