Release 4.2.0

What was added/updated

updated default log handler color names due to ansi lib updates; no breaking changes.

Release 4.1.0

What's new?

• changed to use new ansi library for colors to keep things DRY in multiple projects.

Release 4.0.1

What was fixed?

if there was a $GOPATH defined on the system, but the code wasn't under it an out-of-range exception was thrown, this was identified by @sm3142 in pull request #7 and fix has been made to all handlers.

Thanks @sm3142 for the pull request!

Release 4.0.0

What's New?

• updated syslog to use github.com/RackSec/srslog. std lib syslog will no longer be maintained as per comment golang/go#13449 (comment)
• TLS support is now available via new syslog package
• Simplified Syslog New() function
• eliminated some data races IN THE TESTS, NOT THE LIBRARY ITSELF

Release 3.1.0

What's New?

• Added HipChat log handler for sending critical errors to a HipChat room
• Added godocs for all handlers + update README with links to each.

Release 3.0.1

What Now?

• updated http handler to be an interface to allow for other handlers can be based on it.

Apologies in advance this was supposed to be in the v3.0 changes.

Release 3.0.0

What's New?

• Updated to pass handlers struct to FormatFunc + added a bunch of Getters to more easily provide your own custom formatting. see commit 4b4ebd1 for details
• Changed DisplayColor(...) to SetDisplayColor(...) for naming consistency.

NOTE: this should be the last major version bump for quite a while.

Release 2.3

What's New?

• Added new Email log handler; it uses gomail library form sending the emails.

What! Why?

Only a crazy person would send all logs via email! and you'd be right! 😄 but that's not it's intended use.
Here's how I'm going to use it, by registering 3 separate email handlers I can automatically:

1. Send all errors produced by the application to the developers email group.
2. Send all Warnings and Panics to the Senior Developer.
3. Send all Alerts and Fatals directly to the COO of Development ... you get the picture.

it basically allows for near realtime notification of problems with your app(s)

Release 2.2

What's New?

• Added StackTrace() function to easily capture a stack trace and put it a log Entry's Field
• Added WithFields(...) function to the Entry object so that one can call like so:

log.StackTrace().WithFields(log.F("key","value")).Debug("What Happened?")

Release 2.1

What Changed?

Added RedirectSTDLogOutput(...) to console handler to allow capturing of all std log messages by setting the output of the std logger to pipe to the log library.