https://github.com/opencoff/go-logger

Enhanced logger derived from golang's standard lib
https://github.com/opencoff/go-logger

backtrace go-logger go-logging log-crit logging-library priority syslog

Last synced: 8 days ago
JSON representation

Enhanced logger derived from golang's standard lib

• Host: GitHub
• URL: https://github.com/opencoff/go-logger
• Owner: opencoff
• Created: 2018-02-28T22:35:28.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2024-11-26T04:26:21.000Z (26 days ago)
• Last Synced: 2024-11-26T05:24:02.099Z (26 days ago)
• Topics: backtrace, go-logger, go-logging, log-crit, logging-library, priority, syslog
• Language: Go
• Size: 61.5 KB
• Stars: 4
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# go-logger - Level based logger with sub-logger support

## What is it?

Borrowed from golang stdlib, this enables logging at increasing

levels of verbosity. The verbosity increases as we go down the list

below:

- Emergency (LOG_EMERG) - will halt the program after

  printing a backtrace of the calling goroutine.

- Critical (LOG_CRIT)

- Error (LOG_ERR) - all levels at and above will print a stack-trace

  of the calling goroutine.

- Warning (LOG_WARNING)

- Informational (LOG_INFO) - this is the level at which I log

  most informational messages useful for troubleshooting

  production issues.

- Debug (LOG_DEBUG) - this is the most verbose level

## List of enhancements from the stdlib

- All I/O is done asychronously; the caller doesn't incur I/O cost

- A single program can have multiple loggers - each with a different

  priority.

- An instance of a logger is configured with a given log level;

  and it only prints log messages "above" the configured level.

  e.g., if a logger is configured with level of INFO, then it will

  print all log messages with INFO and higher priority;

  in particular, it won't print DEBUG messages.

- A single program can have multiple loggers; each with a

  different priority.

- The logger method Backtrace() will print a stack backtrace to

  the configured output stream. Log levels are NOT

  considered when backtraces are printed.

- The Panic() and Fatal() logger methods implicitly print the

  stack backtrace (upto 5 levels).

- DEBUG, ERR, CRIT log outputs (via Debug(), Err() and Crit()

  methods) also print the source file location from whence they

  were invoked.

- New package functions to create a syslog(1) or a file logger

  instance.

- Callers can create a new logger instance if they have an

  io.writer instance of their own - in case the existing output

  streams (File and Syslog) are insufficient.

- Any logger instance can create child-loggers with a different

  priority and prefix (but same destination); this is useful in large

  programs with different modules.

- Compressed log rotation based on daily time-of-day (configurable ToD) -- only

  available for file-backed destinations.

- Wrapper available to make this logger appear like a stdlib logger;

  this wrapper prints everything sent to it (it's an io.Writer)