[🐛 BUG]: AppLogger. JSON duplicate "logger" key

[gam6itko]

No duplicates 🥲.

• I have searched for a similar issue in our bug tracker and didn't find any solutions.

What happened?

If we pass key "logger" in context then RR display invalid JSON log with two "logger" keys.

# .rr.yaml
logs:
  mode: production
  level: debug
  encoding: json

https://github.com/roadrunner-php/app-logger/blob/6be59995a76f03b791702ddbe2b47df48bb16e51/src/Logger.php#L99

We have 4 reserved keys

• level
• ts
• logger
• msg

In this case we have 2 solution:

1. If reserved keys present in context then they will be prefixed with __.

\RoadRunner\Logger\Logger::log("Hello!", [
    'logger'=> 'foo', 
    'ts' => 'foo', 
    'msg' =>'foo',
    'level' => 'foo'
])

Output

{
  "level": "info",
  "ts": 1740209343338036353,
  "logger": "app",
  "msg": "Hello!",
  "__level": "foo",
  "__ts": "foo",
  "__logger": "foo",
  "__msg": "foo"
}

2. Replace original keys.
   I think it is very dangerous because user can pass key "logger" with values ["server", "jobs", "http"].

But it's will be good feature. Because we can pass to logger out php monolog logger channel name for further usage in tools like grafana/loki.

https://spiral.dev/docs/basics-logging/current#send-logs-to-a-specific-channel

Version (rr --version)

2025.3.2

How to reproduce the issue?

\RoadRunner\Logger\Logger::log("Hello!", [
    'logger'=> 'foo', 
    'ts' => 'foo', 
    'msg' =>'foo',
    'level' => 'foo'
])

[rustatian]

Hey @gam6itko 👋🏻
Why not vise-versa? Why not use __logger for your custom output like this:

\RoadRunner\Logger\Logger::log("Hello!", [
    '__logger'=> 'foo', 
    '__ts' => 'foo', 
    '__msg' =>'foo',
    '__level' => 'foo'
])