Log4jmemes.com: for those of us that need a laugh

On a serious note, I think it's a good time to remember to donate some $ to open source, especially the Apache foundation for their incredible work over the years!

Re: Log4jmemes.com: for those of us that need a laugh

#5

Post by Maxburn » Wed, Dec 15, 2021, 3:31 PM UTC

Some of us really needed the laugh, nice.

Re: Log4jmemes.com: for those of us that need a laugh

#6

Post by pddpro » Wed, Dec 15, 2021, 3:32 PM UTC

Is there any comprehensive article that covers what log4j is and just what happened that is so critical that seems to have set the entire world on fire? Disclaimer: I have never heard of or used log4j before in my life.

Re: Log4jmemes.com: for those of us that need a laugh

#7

Post by linkdd » Wed, Dec 15, 2021, 3:32 PM UTC

The one about using print/console.log/whatever lol.

I've always done this, never have I used a library for this, because:

  - running manually? >myapp.log 2>&1
  - using systemd? use journalctl
  - using docker/kubernetes? capture automatically the stdout/stderr of your containers and pipe them through logstash or something

Real question: why would an application need to know where its logs go? This is not in the business perimeter, but the ops perimeter. Am I wrong?

EDIT:

Most responses are about configuring logging level, output format, etc... This can be done with a print-based approach without sending a request to an external service (which would need to trust you and your inputs).

Example: Python's default logging module.

Still, thank you for your insightful answers :)

Re: Log4jmemes.com: for those of us that need a laugh

#8

Post by hwers » Wed, Dec 15, 2021, 3:35 PM UTC

Somewhat with shame in the back of my mind, memes like these always tend to help me get the bigger picture of something faster than a long article.

Re: Log4jmemes.com: for those of us that need a laugh

#9

Post by progval » Wed, Dec 15, 2021, 3:37 PM UTC

linkdd wrote: post #7

The one about using print/console.log/whatever lol. I've always done this, never have I used a library for this, because: - running manually? >myapp.log 2>&1 - using systemd? use journalctl - using docker/kubernetes? capture automatically the stdout/stderr of your containers and pipe them through logstash or something Real question: why would an application need to know where its logs go? This is not in the business…

Built-in logging libraries offer more flexibility: you can set the log level of each module to avoid flooding your log files with everything's debug logs, for example. Or you want to write multiple log files with different settings.

Also legacy; before systemd/docker/kubernetes, applications had to send to syslog themselves.

Re: Log4jmemes.com: for those of us that need a laugh

#10

Post by randomNumber7 » Wed, Dec 15, 2021, 3:37 PM UTC

linkdd wrote: post #7

The one about using print/console.log/whatever lol. I've always done this, never have I used a library for this, because: - running manually? >myapp.log 2>&1 - using systemd? use journalctl - using docker/kubernetes? capture automatically the stdout/stderr of your containers and pipe them through logstash or something Real question: why would an application need to know where its logs go? This is not in the business…

> Am I wrong?

You are not a real Java Programmer then.