println!("Let's talk about logging") #802
bobmcwhirter
started this conversation in
General
Replies: 4 comments 1 reply
-
🤣 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
yes 👍 |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I agree and I think this relates to #756 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Let's take a moment and think about logging. I understand the irony of this, given I'm Mr.
println!.I think certainly INFO/WARN/ERROR have their place, but we should use them to express information relevant to operators of the system. The admin who might check logs or dig around in splunk.
For things like "this SBOM is bad", we need to surface that to the UI somehow, as the SRE operating the system probably won't care.
For our purposes, DEBUG/TRACE can exist for "this SBOM is bad" sorta thing, generally suppressed.
Yeah? No?
Beta Was this translation helpful? Give feedback.
All reactions