Question 1

How to add custom fields to logs in azer/logger?

Accepted Answer

Use the logger.Attrs map when calling log methods, like log.Info("message", logger.Attrs{"key": "value"}), which adds key-value pairs to the structured JSON output as shown in the Attributes section.

Question 2

Does logger support log rotation out of the box?

Accepted Answer

No, the README doesn't mention built-in log rotation; it's a minimalistic library focused on output formatting and filtering, so you'd need to handle log file management externally or with custom hooks.

Question 3

How to filter logs by package in production with logger?

Accepted Answer

Set the LOG environment variable with package names, e.g., LOG=images,database, as explained in the Filters section. This works in any environment, but requires restarting the app for changes.

Question 4

logger vs logrus: which is better for Go applications?

Accepted Answer

logger is lighter and simpler with silent-by-default and JSON output, while logrus offers more features and a larger ecosystem. Choose logger for minimalism and production-tested simplicity, or logrus for broader functionality.

Question 5

Is azer/logger thread-safe for concurrent use?

Accepted Answer

The README doesn't explicitly address thread safety, but since it's a logging library designed for production, it likely handles concurrency, though you should test or check the source code for guarantees.

Question 6

How to output logs to a file instead of stdout?

Accepted Answer

Implement a custom writer hook as shown in the Programmatical Usage section, where you can define a Write method to direct logs to a file or other destinations.

logger

What is logger?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions