feat: add request id to default log level

[Hweinstock]

Problem

requestId is the single most important piece of information for the backend team in order to effectively debug these issues and its only visible at the trace level.

Solution

log it by default at info level, along with the rest of the response metadata.

Example Logs

2025-04-30 19:06:55.971 [info] [Info  - 7:06:55 PM] [2025-04-30T23:06:55.966Z] generateAssistantResponse Response: {
  "httpStatusCode": 200,
  "requestId": "1e8a80f1-4d78-47fe-933d-ffe9f29efafe",
  "attempts": 1,
  "totalRetryDelay": 0
}

License

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[jguoamz]

can we still keep this?

[Hweinstock]

is any of the non-metadata info useful? This is what I see:

{
  "$metadata": {
    "httpStatusCode": 200,
    "requestId": "046690bd-6d69-4e1f-a68a-8f302dfd0264",
    "attempts": 1,
    "totalRetryDelay": 0
  },
  "conversationId": "",
  "generateAssistantResponseResponse": {
    "options": {
      "messageStream": {
        "options": {
          "inputStream": {},
          "decoder": {
            "headerMarshaller": {},
            "messageBuffer": [],
            "isEndOfStream": false
          }
        }
      }
    }
  }
}

[jguoamz]

I think you are right, they are not useful because the response is being streamed back, we can remove it here. Do we have logs in response streaming (during parsing)?

[Hweinstock]

We have some for when we identify tool use events, and when errors occurs. See implementation here.

Are there any other important cases that might be helpful for debugging?

[jguoamz]

nit: generateAssistantResponse ResponseMetadata: ${loggingUtils.formatObj(response.$metadata)}