4 ms·
Good points. As I added in the comments to the post, you should be able to turn the logging/tracing on or off on a running system. Furthermore, you need to be a
by henrik_w 14y ago
Good points. As I added in the comments to the post, you should be able to turn the logging/tracing on or off on a running system. Furthermore, you need to be able to select what what should be logged, for example only messages to a certain mobile phone. Simply logging everything will swamp the system.
My main point was this: if you don't get the results you expected, do you know where to start looking for the problem or not? If you have no idea, then there is not enough logging/tracing present in the program.
- rumcajz 14y ago"As I added in the comments to the post, you should be able to turn the logging/tracing on or off on a running system. Furthermore, you need to be able to select what what should be logged, for example only messages to a certain mobile phone." There's little to gain that way. If the logging was off when the problem happened, you have no logs. You can switch it on and try to reproduce. However, if you are able to reproduce, you can as well attach the process to the debugger and check what's happening. No logging needed.
- henrik_w 14y agoAttaching a debugger is not always an option - if you set break-points things will start timing out. Also, you can ask operations people to enable certain logging on a system, but you can't ask them to attach a debugger.
- AlisdairO 14y agoThis depends very much on the type of business you're running. If you're creating software to run yourself, fair enough (as long as your debugger is sufficiently low overhead). If you're selling (and supporting) software for other people, on the other hand, being able to get them to turn on logging on a certain class and try again is a godsend.