Error Levels for Custom Log Targets are not working

[TheFox]

Description

Consider this settings:

// app.php
return [
    'components' => [
        'log' => function () {
            $logConfig = craft\helpers\App::logConfig();

            // Email Target
            $logConfig['targets'][] = [
                'class' => EmailTarget::class,
                'levels' => ['warning', 'error'],
                'message' => [
                    'from' => ['error@example.com'],
                    'to' => ['error@example.com'],
                    'subject' => 'My Project ERROR',
                ],
                'logVars' => [],
            ];

            // Instantiate and return the component.
            return Craft::createObject($logConfig);
        },
    ],
];

Then, very often, I get emails with the following text:

2019-02-01 10:37:14.312 +0100 [info][craft\queue\QueueLogBehavior::beforeExec]  [96] Deleting stale template caches (attempt: 1) - Started
...

This should not happen since I have only subscribed warning and error.

Steps to reproduce

1. Create custom log target.
2. Wait for it.

Additional info

• Craft version: Craft Pro 3.1.6.1
• PHP version: 7.2.13
• Database driver & version: MySQL 5.5.5

[brandonkelly]

This is going to be a Yii bug, if not just an issue with how you’re configuring it. Can you please report it over at https://github.com/yiisoft/yii2/issues ?

[TheFox]

Ok, I'll. Thanks.

[erktime]

@brandonkelly I recently had the same issue. I don't believe this is a YII bug but instead a Craft bug. Craft's custom QueueLogBehavior modifies all log targets setup for the site. Look at your code:
https://github.com/craftcms/cms/blob/develop/src/queue/QueueLogBehavior.php#L89

You override the except and levels for every log target, not just the default file target that craft uses by default.

[brandonkelly]

Doh, you are correct @erktime. 😞

[brandonkelly]

Fixed for the next release.

To get the fix early, change your craftcms/cms requirement in composer.json to:

"require": {
  "craftcms/cms": "dev-develop#34e1fef8ee10754014ab1bc986b682ef5f0fa4a9",
  "...": "..."
}

Then run composer update.

[erktime]

Team work 👍