Blog / Standard Library

Handler configuration

April 14, 2026

The default slog handlers are quite configurable.

Overview

…

Both TextHandler and JSONHandler can be configured with HandlerOptions. There are options for setting the minimum level (see Levels, below), displaying the source file and line of the log call, and modifying attributes before they are logged.

While HandlerOptions only exposes three fields:

  • AddSource bool
  • Level Leveler
  • ReplaceAttr func(groups []string, a Attr) Attr

The last one provides an immense amount of flexibility, letting you filter, replace, or augment log key/value pairs as they are processed. This lets you do things like filter out sensitive or noisy log information, or add additional details to errors, etc.

That said, the option you’re most likely to use the most is the simpler Level field. This lets you set the level for the handler—only want ERROR or higher logs to go to a particular place? This is where you control that.

And AddSource instructs the handler to compute the source code position of the log statement and add a SourceKey attribute to the output.

Share this

Direct to your inbox, daily. I respect your privacy .

Unsure? Browse the archive .

Related Content

Chosing an slog handler

log/slog ships with two default handlers: the TextHandler and the JSONHandler. Overview … For more control over the output format, create a logger with a different handler. This statement uses New to create a new logger with a TextHandler that writes structured records in text form to standard error: logger := slog.New(slog.NewTextHandler(os.Stderr, nil)) TextHandler output is a sequence of key=value pairs, easily and unambiguously parsed by machine. This statement: logger.Info("hello", "count", 3) produces this output:

Log levels

I'm launching a new live course: **Idiomatic Testing in Go**. The course begins May 5. Early-bird pricing is in effect until April 28. Why Go avoids assert libraries Better alternatives to mocks Make writing tests fun! See pricing & reserve → log/slog provides some rather sophisticated capabilities around log levels. We’ll get into it, but the good news is, you don’t need to care about how sophisticated it can get, if you don’t care.

Logging common fields

It’s common that you’ll want to include certain attributes in all logs in an application or component. log/slog makes this pretty easy. Overview … Some attributes are common to many log calls. For example, you may wish to include the URL or trace identifier of a server request with all log events arising from the request. Rather than repeat the attribute with every log call, you can use Logger.With to construct a new Logger containing the attributes:

Get daily content like this in your inbox!

Subscribe