Developers, DevOps practitioners, and managers sometimes refer to log levels as severity levels. Log levels describe the relative importance of the event (with terms such as debug, info, warning, error, and fatal) and the density level of information from the logging framework. Having a severity attribute helps to filter out or discard less critical information so that you can look for critical errors solely.
Effective use of log levels can limit the amount of data, reduce the cost of using a centralized log management tool, and keep search results speedy. In some instances, it might not be possible for you to control how applications generate logs, but the log management system can also discard unwanted data. Once in New Relic One, you can surface outliers using machine learning-driven patterns based on the log level. Color-coded log levels also give you a visual indicator to focus your attention on the most critical areas.
Please note that you should use log levels with care, particularly when using the debug log level. Debug can be very helpful when you need to capture very verbose messages associated with a specific behavior, but if you use it unnecessarily, it can create a significantly higher volume of logs and slow your ingestion and search functions without providing any additional value. It may be beneficial for larger teams and projects to communicate a standard for log levels so that grouping, categorizing, and logging methods are consistent.