|
|
|
|
|
by skissane
1806 days ago
|
|
> If there's some tricky bug in production, then one can create some sort of debugging service that runs on another port and deploy it to investigate the bug, If you are under time pressure to fix an escalation from a high profile customer, and you don't have such a service yet, do you make the customer wait for you to write one, or do you just use command line access? Or else, if you already have such a service, but it doesn't contain the necessary diagnostics to investigate this particular problem, do you make the customer wait for you to enhance it, or do you just use command line access? Or you make your debug service totally generic – allow it to run arbitrary code supplied by the user – in which case it can do anything the command line can, but how is that actually any more secure than more standard means of command line access? Plus, it is going to be adding friction which may slow down resolution. > or use management and monitoring tools. Often these work fine for some problems, and then you get a problem which they don't cover adequately, and you need to go beyond them. |
|