Programming

17528 readers

295 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

337

What are your programming hot takes? (lemmy.ml)

submitted 1 year ago by 257m@lemmy.ml to c/programming@programming.dev

895 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] onlinepersona@programming.dev 1 points 1 year ago (1 children)

So, error logs, warnings, informational, and debug logs should all just go to stdout at all times, no --verbose or -vvv should exist, everyone who wants to filter logs will have to pipe it through grep or some other program to help filter the logs? Or am I understanding that incorrectly?

[–] xantoxis@lemmy.world 1 points 1 year ago (1 children)

Yep, that's the take. Or you aggregate logs and search them through a search interface. Or you output structured logs, and use structured search.

[–] onlinepersona@programming.dev 2 points 1 year ago* (last edited 1 year ago)

The take