[shivanee-p]

This pull request adds logCall, buildLogAttributes, and getGaxLogger to LoggerHelper.

Key Changes:

• Added getGaxLogger in LoggerHelper.ts to resolve the google-logging-utils logger for gcp.client.service (defaulting to 'google-gax').
• Added buildLogAttributes in LoggerHelper.ts to populate shared structured log attributes (gcp.client.*, rpc.system.name, url.domain, rpc.method, rpc.response.status_code / http.response.status_code, error.type, gcp.errors.domain, and gcp.errors.metadata.<key>).
• Added logCall in LoggerHelper.ts to wrap promise, callback, stream, and synchronous execution boundaries with a one-time latch (hasLoggedL3) and emit a WARNING log with exception.type, exception.message, exception.stacktrace, and active trace/span correlation (telemetryTraceId, telemetrySpanId).
• Exported getPromiseTarget from TracerHelper.ts for shared promise/thenable detection.

[gemini-code-assist]

Code Review

This pull request introduces structured logging for API calls in Google GAX. It adds LoggerHelper.ts with utilities like getGaxLogger, buildLogAttributes, and logCall to emit structured warning logs when logical requests fail across promises, callbacks, streams, or synchronous boundaries. It also exports getPromiseTarget from TracerHelper.ts and includes comprehensive unit tests in loggerHelper.ts. The review feedback recommends replacing a potentially unsafe typeof err === 'object' check with err instanceof Error to prevent runtime errors when handling null or prototype-less objects.

[quirogas]

Reviewed #9756 against the Milestone 2 Error Logging design doc and live gRPC/REST (fallback: 'rest') error payloads. Approving to unblock merging once the 3 inline items below (and 1 minor nit) are addressed.

[quirogas]

Nit: If buildInitialAttributes (contextUtil.ts) omits undefined properties, buildLogAttributes does not need the Object.entries loop or (attributes as Record<string, unknown>)[key] = value cast. Also on line 198, exceptionMessage || err falls back to err when err is new Error('') (empty message), causing util.format('%s', err) to format the full stack trace into the log message; use exceptionMessage || String(err).