Open jaredhirsch opened 9 years ago
They're less understandable to me. I don't know what to do with so many high-severity levels. And I found it's useful to have noiser levels than debug
.
@6a68 are you using mozlog?
yup, chronicle is using it. one of the things I'd like to do is map bad stuff to pagerduty, which I can do with the current set of log levels, but I dislike having to tell ops people "I'm going to log using a random subset of the syslog levels, but they mean totally different things, since the highest severity ones are missing"
Fair enough. I'd welcome a intel.setLevels() method...
On Thu, Feb 19, 2015, 10:55 AM Jared Hirsch notifications@github.com wrote:
yup, chronicle is using it. one of the things I'd like to do is map bad stuff to pagerduty, which I can do with the current set of log levels, but I dislike having to tell ops people "I'm going to log using a random subset of the syslog levels, but they mean totally different things, since the highest severity ones are missing"
— Reply to this email directly or view it on GitHub https://github.com/seanmonstar/intel/issues/33#issuecomment-75112715.
syslog gives us emerg, alert, crit, err, warn, notice, info, debug. These log levels have well-defined and widely understood (by ops type people) meanings. If intel is going to provide a standard set of hierarchical loggers, why not those?