Releases: go-diary/diary
Releases · go-diary/diary
Go Version Upgrade
Enhanced HumanReadableHandler Output
Include the log meta data into the terminal output as a JSON pretty print string. This will help simplify debugging of applications while in a local development environment.
Audit Tracking
Allow tracking of audit level logs, audit level logs will always be tracked regardless of log level set. And should be used to keep track of major events for the single goal of auditing the workflow or system using the logs.
Minor Enhancement
Ability to return parent diary for a given page
Minor Bug Fix
Fixed IsValidLevel
function issue
First Useable Version
This release houses the most basic of functionality which is to:
- write application logs at different levels (trace, debug, info, notice, warning, error, fatal) in a way that can be easily queried on a database or something like newrelic logs interface.
- to pass request context between microservices in order to link logging to a single request chain, meaning that you can query the entire sequence of events that occurred in a given request.
- to pass log level setting between microservices allowing you to customise logging level for specific API endpoints or specific microservice functions.