2 ms·
Error handling, which includes logging the error, should almost always be the responsibility of the caller. Only the caller knows why the call was made, and onl
by twblalock 10y ago
Error handling, which includes logging the error, should almost always be the responsibility of the caller. Only the caller knows why the call was made, and only the caller knows the impact of the error on what the caller is trying to do.
- paulddraper 10y agoExactly. You run a process that exits with a non-zero code. Is that an error that should be logged? Or just informational? (E.g. `diff`.) You request an HTTP resource that doesn't exist. Loggable error? Or normal result? Only the caller knows.
- tedsuo 10y agoI recommend separating collection from instrumentation. Always instrument at the source, so that you can instrument the flow of your entire application. If the caller decides there is something about the code flow that is worth recording, it can trigger collection of the entire trace.