v1.5.12

• Add redirect standard log functions

v1.5.11

• Fix missing field in copy fields to child logger.

v1.5.10

Changed

• Fixed New, was missing setting defaultIoWriterLevel, fields, status.
• Changed default io.Writer level to None.

v1.5.9

Added

• For convenience, conforms with io.Writer interface. Default level: error. SetIoWriterLevel changes the default level.

Changed

• Fixed chained example.
• Lowercased all levels.
• It now warns when an application tries to write to a closed writer.

v1.5.8

• All SetXYZ methods returns its proper interface allowing method chaining.
• Breakpoint is now variadic.
• Properly handle cases where sypl writes to a piped output, but it's broken.

v1.5.7

• Fixed ExampleNew_globalFields test.

v1.5.6

Added the ability to set breakpoints. If a Breakpoint is set it'll stop execution waiting the user press /n ("enter") to continue. It helps users doing quick, and effective log-to-console debug. A message with the breakpoint name, and PID of the process will be printed using the debug level. Arbitrary data can optionally be set - if set, it'll be printed. Errors are printed using the standard error level. Set logging level to trace for more.

Previously, flow would look like:

• Log markers are set, e.g.: logger.Debugln("Here 1", whatever)
• Application runs
• Scan visually output, or a file - via grep for the markers.

Now:

• Named Breakpoints are set
• Application runs
• Breakpoint is hit. Information about it is printed.
• Runtime is paused, allowing analysis of data - if any, right way. Additionally, an external and more advanced debugger can be attached.
• Dev controls the flow, pressing enter at any time, continue.

v1.5.5

• Exported sypl.Name to deal with golang/go#5819.

v1.5.4

• Renamed logging component filtering env var from SYPL_DEBUG to SYPL_FILTER.

---

In a application with many loggers, and child loggers, sometimes more fine control is needed, specially when debugging applications. Sypl offers two powerful ways to achieve that: SYPL_FILTER, and SYPL_DEBUG env vars.

SYPL_FILTER allows to specify the name(s) of the component(s) that should be logged, for example, for a given application with the following loggers: svc, pv, and cm, if a developer wants only to see svc, and pv logging, it's achieved just setting SYPL_FILTER="svc,pv".

SYPL_DEBUG allows to specify the max level, for example, for a given application with the following loggers: svc, pv, and cm, if a developer sets:

• SYPL_DEBUG="debug": any application running using Sypl, any component, any output, will log messages bellow the debug level
• SYPL_DEBUG="console:debug": any application running using Sypl with an output called console, will log messages bellow the debug level
• SYPL_DEBUG="warn,console:debug": any application running using Sypl, any component, any output, will log messages bellow the warn level, AND any application running using Sypl with an output called console, will log messages bellow the debug level.

NOTE: warn is specified first. Only for this case - global scope, it's a requirement.
SYPL_DEBUG="console:debug,warn": In this case warn will be discarded!.

• SYPL_DEBUG="svc:console:debug": any application running using Sypl with a component called svc with an output called console, will log messages bellow the debug level
• SYPL_DEBUG="file:warn,svc:console:debug": any application running using Sypl with an output called file will log messages bellow the warn level, and any application running using Sypl with a component called svc with an output called console will log messages bellow the debug.

Possible scopes:

• {componentName:outputName:level}: Component, and output scoped
• {outputName:level}: Output scoped
• {level}: Global scope

The possibilities are endless! Checkout the debugAndFilter example for more.

v1.5.3

• Fix bug where setting fields for a message would set globally too.