# README
Logger implements a shared logging infrastructure. It add several features on top of the standard logging package:
- The usual log levels, from trace up to panic.
- Logs are created for named services, each of which can log at its own log level.
- Eacch log has a group number that can be used to group related log entries.
- Each log entry has a globally unique sequence number that can be used to reconstruct the order in which log entries were generated even in the face of out-of-order log recording.
- Logs can have callback functions registered for them to facilitate sending log entries as events.
# Packages
hcl implements compatibility with github.com/hashicorp/go-hclog.
# Functions
New returns a new Buffer which will write to the passed-in Local logger.
ParseLevel returns the log level appropriate for the passed in string.
# Constants
Audit logs must always be printed.
Debug should be useful for debugging low-level problems that do not necessarily require the level of detail that Trace provides.
Error should be used to signal when something unusal happened that could not be handled gracefully, but that did not result in a condition where we had to shut down.
Fatal should be used where we need to shut down the program in order to avoid data corruption, and there is no possibility of handling in a programmatic fashion.
Info should be used to emit information messages that do not signal an unusual condition.
Panic should be used where we need to abort whatever is happening, and there is a possibility of handling or avoiding the error in a programmatic fashion.
Trace should be used when you want detailed log messages that map to the actual flow of control through the program.
Warn should be used to signal when something unusual happened that the program was able to handle appropriatly.