DI: handlers are global

[mkoubik]

TLDR: Is there any support for multiple channels in a single extension?

I want to log SQL queries separately besides logging exceptions (ideally to have another instance of Monolog\Logger) so I tried to register multiple MonologExtensions like this:

extensions:
    monolog.errors: Kdyby\Monolog\DI\MonologExtension
    monolog.sql: Kdyby\Monolog\DI\MonologExtension

monolog.errors:
    name: errors

monolog.sql:
    name: sql
    registerFallback: no
    hookToTracy: no
    handlers:
        ...

The problem is that handlers from monolog.sql have "global" tag monolog.handler so monolog.errors uses them as well. Instead I would like the tag prefixed (monolog.sql.handler) so you can register the extension multiple times.
Is this a valid solution, should I send PR (it's a BC break)?

[fprochazka]

Interesting solution. But I would preffer having structured configuration of a single extension. Like in Kdyby/Doctrine.

monolog:
    errors:
        name: errors
        handlers: ...

    sql:
        registerFallback: no
        hookToTracy: no
        handlers: ...

but then, the problem with tags remains...

---

I think one tag should remain, but when it has a metadata (tags can have additional meta) then register only to the monolog named as the metadata of the handler tag

services:
    - {class: ..., tags: [monolog.handler]} # this will be registered to all Logger instances
    - {class: ..., tags: [monolog.handler: errors]} # only to instance named "errors"
    - {class: ..., tags: [monolog.handler: sql]} # only to instance named "sql"

[ldrahnik]

Is there any workaround to do that? will be solved? i agree with @mkoubik

[fprochazka]

There is currently no workaround I'm aware of.

I'm working a bit with symfony now, so I intent to copy their style of configuring monolog, since this lib has very weak support for complex channel+handler setups.