Using the log package and understanding when to log errors
Logging should typically occur when an error is the final result. In other words, it's useful to log when something exceptional or unexpected occurs. It might also be appropriate, if you use a log that provides log levels, to sprinkle debug or info statements at key parts of your code to quickly debug issues during development. Too much logging will make it difficult to find anything useful, but not enough logging can result in broken systems with no insight into the root cause. This recipe will demonstrate the use of the default Go log package and some useful options and showcase when a log should probably occur.
Getting ready
Configure your environment according to these steps:
- Refer to the Getting ready section of the Handling errors and the Error interface recipe in this chapter.
- Run the
go get github.com/pkg/errors/command.
How to do it...
These steps cover writing and running your application:
- From your terminal/console application...
