Ability to correlate Error logs with debug logs

[antonmos]

Is your feature request related to a problem? Please describe.
When this error is logged

{"@t":"2025-06-10T14:59:24.4812141+00:00","ThreadId":39,"@x":"System.ArgumentException: Read size too big, should be less than 4096 items\n   at EventStore.Core.Services.Storage.StorageReaderWorker`1.ReadStreamEventsBackward(ReadStreamEventsBackward msg) in /home/runner/work/TrainStation/TrainStation/EventStore/src/EventStore.Core/Services/Storage/StorageReaderWorker.cs:line 384","@i":902380009,"ProcessId":1,"@l":"Error","SourceContext":"EventStore.Core.Services.Storage.StorageReaderWorker"}

the log entry does not have any metadata that can be used to correlate it with the request the caused it.

In my case, due to low load, it was easy to see this debug log entry

{
  "dateTime": "2025-06-10T14:59:24.4806854+00:00",
  "RequestPath": "/streams/$et-LoanApplicationExpired/78365/backward/4999",
  "headers": {
    "Accept": [
      "application/json"
    ],
    "l5d-client-id": [
      "default.staging-use1.serviceaccount.identity.linkerd-system.cluster.local"
    ],
    "User-Agent": [
      "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:139.0) Gecko/20100101 Firefox/139.0"
    ],
    "Referer": [
      "http://esdb-2.esdb-headless.staging-use1.svc.cluster.local:2113/web/index.html"
    ],
    "Host": [
      "esdb-2.esdb-headless.staging-use1.svc.cluster.local:2113"
    ],
    "Accept-Encoding": [
      "gzip, deflate"
    ],
    "Accept-Language": [
      "en-US,en;q=0.5"
    ],
    "es-longpoll": [
      "5"
    ]
  },
  "RequestId": "0HND2SF79LI8Q:00000001",
  "@i": 1844820351,
  "@l": "Debug",
  "httpMethod": "GET",
  "body": "",
  "SourceContext": "EventStore.Transport.Http.EntityManagement.HttpEntityManager",
  "ConnectionId": "0HND2SF79LI8Q",
  "@t": "2025-06-10T14:59:24.4806999+00:00",
  "ThreadId": 39,
  "requestUrl": "http://esdb-2.esdb-headless.staging-use1.svc.cluster.local:2113/streams/$et-LoanApplicationExpired/78365/backward/4999?embed=tryharder",
  "ProcessId": 1,
  "remoteEndPoint": "10.143.166.162:55192"
}

Describe the solution you'd like

The error log entry could have some information also included in the debug entry - for example RequestId or ConnectionId

Describe alternatives you've considered

• Using timestamps to find related logs - not an effective solution under load

Additional context
Add any other context or screenshots about the feature request here.

[linear]

DB-799 Ability to correlate Error logs with debug logs