Logging Libraries Debate

Discussions revolve around logging libraries and frameworks, including criticisms of complex ones like log4j due to vulnerabilities and side effects, preferences for simpler no-code or structured alternatives like slog, and ideal features for logging solutions.

➡️ Stable 0.5x DevOps & Infrastructure
2,989
Comments
19
Years Active
5
Top Authors
#3685
Topic ID

Activity Over Time

2008
6
2009
8
2010
28
2011
53
2012
115
2013
101
2014
105
2015
84
2016
137
2017
76
2018
102
2019
128
2020
140
2021
642
2022
353
2023
340
2024
220
2025
339
2026
12

Keywords

e.g JSON EOL InfoContext NewWebConsoleHandler github.com STD API NewTextHandler Level.Info logging logs log library message framework libraries handlers level severity

Sample Comments

marvinblum • Aug 22, 2020 • View on HN

"No Code Logging Library" would be even better ;)

tptacek • Dec 21, 2016 • View on HN

Which logging systems did you like/not like?

This is what log/slog is for!

Matl • Sep 10, 2024 • View on HN

Wouldn't you use slog if you want logging friendly?

colejohnson66 • Dec 11, 2020 • View on HN

Would this make sense in a logging situation?

eatonphil • Jun 11, 2022 • View on HN

Why are so many people using log4j or any complex logging library in the first place?

perihelions • Sep 10, 2023 • View on HN

It's a logging framework! :D

lanstin • Dec 18, 2021 • View on HN

Truthfully most log libraries are not going to have such a flaw.

rascul • Dec 5, 2025 • View on HN

Could you describe what you would consider a good logging solution?

lazyasciiart • Mar 29, 2024 • View on HN

Until the discovery of a log4j-equivalent, then suddenly it's not fine.