Laravel日志级别数值相关技术疑问：为何用百级值、是否遵循标准等

First, let's recap the log level values you noted—they’re tied directly to how Laravel’s underlying logging system operates:

'emergency' => 100
'alert' => 200
'critical' => 300
'error' => 400
'warning' => 500
'notice' => 600
'info' => 700
'debug' => 800

Now let’s break down each of your questions:

1. Why use hundred-level values instead of a simple 8-1 scale? #

The core reason is extensibility. Using 100-point increments leaves plenty of breathing room to add custom log levels between the standard ones later on. For example, if you needed a level between critical (300) and error (400), you could define something like 'critical_error' => 350 without disrupting the existing hierarchy. A tight 8-1 scale wouldn’t offer this flexibility—you’d have to reorder or squeeze in levels, which would break consistency with existing code and community standards.

2. Do these values follow a specific convention, RFC, ISO, or standard? #

Yes! Laravel relies on Monolog for its logging functionality, and Monolog adheres to the PSR-3: Logger Interface standard from the PHP Framework Interoperability Group (PHP-FIG). PSR-3 explicitly defines these exact numeric values for each log level to ensure consistency across PHP logging libraries. While it’s not an official RFC or ISO standard, it’s a widely adopted community standard that most PHP frameworks and logging tools follow.

3. Does Laravel actually use these numeric values in practice? #

Absolutely. When you configure your log level (e.g., setting LOG_LEVEL=warning in your .env file), Laravel converts that string name to its corresponding numeric value (500) internally. This number is used to filter which logs get recorded: any log with a value less than or equal to your configured level will be processed. For example, if you set the level to warning, logs labeled emergency (100) up to warning (500) are kept, while info (700) and debug (800) are ignored. These values also come into play if you’re building custom log handlers or filtering logs programmatically.

4. Can special log events generate other numeric values? #

By default, no—Laravel sticks strictly to the eight standard levels and their associated values from PSR-3/Monolog. However, if you need to create custom log levels for niche application-specific use cases, you can extend Monolog to add new levels with your own numeric values (like 350 for a custom critical_warning level). But these are non-standard and entirely up to your application’s needs—Laravel doesn’t generate them out of the box.

内容的提问来源于stack exchange，提问作者fudo