[telemetry improvement]: emit sql_operation, auth_type, driver_connection_params - ship even if null

[samikshya-db]

Summary

Although these can be extracted from close monitoring of logs, it is good to populate these upfront. The producer + aggregator already had the data; the exporter was dropping it on the floor and the receiver-side rows were showing up with empty sql_operation and missing auth_type / driver_connection_params.

• sql_operation.operation_detail.operation_type — on both connection (CREATE_SESSION / DELETE_SESSION) and statement (EXECUTE_STATEMENT / LIST_*) events. Already aggregated, just not exported.
• sql_operation.is_compressed — surfaced from the aggregator's existing compressed flag (true-on-any-CloudFetch-chunk).
• sql_operation.execution_result — mapResultFormatToTelemetryType(undefined) now resolves to FORMAT_UNSPECIFIED (matching its existing default-case fallback) instead of undefined. This makes the existing if (metric.resultFormat || ...) gate light up for DDL/DML and SELECTs that were closed without iterating rows, so every statement-complete row gets a populated sql_operation block.
• Top-level auth_type — from DriverConfiguration.authType.
• New top-level driver_connection_params block — host_info.host_url, http_path, enable_arrow, enable_direct_results, socket_timeout, enable_metric_view_metadata, cloud_fetch_enabled, lz4_enabled, retry_max_attempts, cloud_fetch_concurrent_downloads. Field names mirror the JDBC DriverConnectionParameters schema.

auth_type and driver_connection_params are gated behind the same includeCorrelation (authenticated-export) guard as system_configuration — host_url and http_path are workspace-correlated identifiers and must not ship on the unauthenticated endpoint. Existing test omits workspace_id, session_id, statement_id from unauth payload continues to enforce that contract.

driverConfig only rides on connection metrics today, so the new top-level blocks ride along with CREATE_SESSION / DELETE_SESSION events; receivers can join statement-level rows to the corresponding connection row by session_id.

Test plan

• npm run type-check (build) — clean
• npx mocha --require ts-node/register tests/unit/telemetry/*.test.ts — 300 passing
• Re-run the lumberjack query (entry.sql_statement_id is not null) after deploy and confirm sql_operation is non-null on every statement row and carries operation_detail.operation_type
• Confirm entry.auth_type and entry.driver_connection_params.host_info.host_url populate on CREATE_SESSION rows in the authenticated stream and remain absent in the unauthenticated stream

This pull request and its description were written by Isaac.

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).

[github-actions]

Thanks for your contribution! To satisfy the DCO policy in our contributing guide every commit message must include a sign-off message. One or more of your commits is missing this message. You can reword previous commit messages with an interactive rebase (git rebase -i main).