Logging in Ruby: (Almost) Everything You Need to Know

Re:Logging in Ruby: (Almost) Everything You Need to Know by software_writer on Sunday July 30, 2023 @04:28PM (#36935607)

It could be useful for logging messages that don't fit a particular category, i.e. a catch-all category, to identify patterns over time.

[ Parent | on HN ]

Re:Logging in Ruby: (Almost) Everything You Need to Know by xyproto on Sunday July 30, 2023 @04:51PM (#36935828)

Can you give an example of a log message that would not fit typical logging levels? (Info/Debug/Error etc)

[ Parent | on HN ]

Re:Logging in Ruby: (Almost) Everything You Need to Know by software_writer on Sunday July 30, 2023 @05:31PM (#36936207)

I was trying to think of a good example, but the following table from RFC 5424 [1] might be a good starting point. I guess unknown could be used for the top 3 conditions.

           Numerical         Severity
             Code

              0       Emergency: system is unusable
              1       Alert: action must be taken immediately
              2       Critical: critical conditions
              3       Error: error conditions
              4       Warning: warning conditions
              5       Notice: normal but significant condition
              6       Informational: informational messages
              7       Debug: debug-level messages

[1] https://datatracker.ietf.org/doc/html/rfc5424

[ Parent | on HN ]