Documentation ¶
Overview ¶
Package mlog implements a thin layer over logr to help enforce mo's logging convention. Logs are always structured as a constant message with key and value pairs of related metadata.
The logging levels in order of increasing verbosity are: error, warning, info, debug, trace and all.
error and warning logs are always emitted (there is no way for the end user to disable them), and thus should be used sparingly. Ideally, logs at these levels should be actionable.
info should be reserved for "nice to know" information. It should be possible to run a production server at the info log level with no performance degradation due to high log volume. debug should be used for information targeted at developers and to aid in support cases. Care must be taken at this level to not leak any secrets into the log stream. That is, even though debug may cause performance issues in production, it must not cause security issues in production.
trace should be used to log information related to timing (i.e. the time it took a controller to sync). Just like debug, trace should not leak secrets into the log stream. trace will likely leak information about the current state of the process, but that, along with performance degradation, is expected.
all is reserved for the most verbose and security sensitive information. At this level, full request metadata such as headers and parameters along with the body may be logged. This level is completely unfit for production use both from a performance and security standpoint. Using it is generally an act of desperation to determine why the system is broken.
Index ¶
- func All(msg string, keysAndValues ...interface{})
- func Always(msg string, keysAndValues ...interface{})
- func Debug(msg string, keysAndValues ...interface{})
- func DebugErr(msg string, err error, keysAndValues ...interface{})
- func Enabled(level LogLevel) bool
- func Error(msg string, err error, keysAndValues ...interface{})
- func Fatal(err error, keysAndValues ...interface{})
- func Info(msg string, keysAndValues ...interface{})
- func InfoErr(msg string, err error, keysAndValues ...interface{})
- func Logr() logr.Loggerdeprecated
- func Setup() func()
- func TestZapOverrides(ctx context.Context, t *testing.T, w io.Writer, f func(*zap.Config), ...) context.Context
- func TestZapr(t *testing.T, w io.Writer) logr.Logger
- func Trace(msg string, keysAndValues ...interface{})
- func TraceErr(msg string, err error, keysAndValues ...interface{})
- func ValidateAndSetKlogLevelAndFormatGlobally(ctx context.Context, klogLevel klog.Level, format LogFormat) error
- func ValidateAndSetLogLevelAndFormatGlobally(ctx context.Context, spec LogSpec) error
- func Warning(msg string, keysAndValues ...interface{})
- func WarningErr(msg string, err error, keysAndValues ...interface{})
- func ZapClock(c clock.Clock) zapcore.Clock
- type LogFormat
- type LogLevel
- type LogSpec
- type Logger
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func Enabled ¶
Enabled returns whether the provided mlog level is enabled, i.e., whether print statements at the provided level will show up.
func TestZapOverrides ¶
func ValidateAndSetKlogLevelAndFormatGlobally ¶ added in v0.0.2
func ValidateAndSetKlogLevelAndFormatGlobally(ctx context.Context, klogLevel klog.Level, format LogFormat) error
Deprecated
func WarningErr ¶
Types ¶
type LogLevel ¶
type LogLevel string
LogLevel is an enum that controls verbosity of logs. Valid values in order of increasing verbosity are leaving it unset, info, debug, trace and all.
const ( // LevelWarning (i.e. leaving the log level unset) maps to klog log level 0. LevelWarning LogLevel = "" // LevelInfo maps to klog log level 2. LevelInfo LogLevel = "info" // LevelDebug maps to klog log level 4. LevelDebug LogLevel = "debug" // LevelTrace maps to klog log level 6. LevelTrace LogLevel = "trace" // LevelAll maps to klog log level 100 (conceptually it is log level 8). LevelAll LogLevel = "all" )
type Logger ¶
type Logger interface { Error(msg string, err error, keysAndValues ...interface{}) Warning(msg string, keysAndValues ...interface{}) WarningErr(msg string, err error, keysAndValues ...interface{}) Info(msg string, keysAndValues ...interface{}) InfoErr(msg string, err error, keysAndValues ...interface{}) Debug(msg string, keysAndValues ...interface{}) DebugErr(msg string, err error, keysAndValues ...interface{}) Trace(msg string, keysAndValues ...interface{}) TraceErr(msg string, err error, keysAndValues ...interface{}) All(msg string, keysAndValues ...interface{}) Always(msg string, keysAndValues ...interface{}) WithValues(keysAndValues ...interface{}) Logger WithName(name string) Logger // contains filtered or unexported methods }
Logger implements the mlog logging convention described above. The global functions in this package such as Info should be used when one does not intend to write tests assertions for specific log messages. If test assertions are desired, Logger should be passed in as an input. New should be used as the production implementation and TestLogger should be used to write test assertions.
func WithValues ¶
func WithValues(keysAndValues ...interface{}) Logger