Logy v0.1is out!

Configurable logger for Go

Clear logging for Go applications

Readable console output, JSON records, contextual fields, and error traces without extra framework work.

Terminal
$go run .
2026-08-21 14:35:10INFOgo.codnect.io/logy:server started
2026-08-21 14:35:11WARNgo.codnect.io/logy:retry scheduled
2026-08-21 14:35:12ERRORgo.codnect.io/logy:request failed
2026-08-21 14:35:13DEBUGgo.codnect.io/logy:handler loaded
2026-08-21 14:35:14TRACEgo.codnect.io/logy:context attached
$

Why Logy

Logy brings together the things Go applications usually assemble around their logger: names, fields, handlers, formats, package rules, and errors.

Named, package, and typed loggers

Create package, named, or typed loggers for the part of the application that produced each record.

Contextual fields

Attach request, trace, tenant, user, or job values through context without changing every log call.

Structured logging

Keep level, logger, message, fields, and errors as record data before choosing console or JSON output.

Multiple destinations

Send records to console, files, syslog, or custom handlers with destination-specific rules.

Fast

Keep logging lightweight on the hot path while still preserving useful fields and logger metadata.

Console and JSON output

Use readable console logs during development and structured JSON records in production.

FAQ

Common questions

A few practical answers about where Logy fits and how its output model works.

Why use Logy instead of the standard logger?+

Logy keeps simple log calls, but adds named loggers, contextual fields, handlers, and production-friendly output when an application needs more structure.

Does structured logging mean JSON only?+

No. Log records can stay structured as level, logger, message, fields, and errors before a handler formats them for console output, JSON, or another destination.

Can Logy fit into an existing Go application?+

Yes. Logy is designed to start small, so packages can adopt named loggers, fields, and handlers gradually without changing the whole application at once.

Discover more

Join the Codnect community

Follow the projects, share ideas, and help shape open source software for developer ecosystems

Community

Build, discuss, and improve developer tools together

Project conversations, release notes, ideas, and early feedback all live close to the code