Connection errors to unauthenticated telemetry endpoint

[saishreeeee]

What type of PR is this?

• Refactor
• Feature
• Bug Fix
• Other

Description

Send error logs to the unauthenticated telemetry endpoint in case of connection/authentication errors (before TelemetryClient initialization)

How is this tested?

• Unit tests

• E2E Tests

• Manually
  Tried to establish a connection with an invalid access token

    === Request Details ===
    URL: https://e2-dogfood.staging.cloud.databricks.com/telemetry-unauth
    
    Headers:
      Accept: application/json
      Content-Type: application/json
    
    Request Body Summary:
      uploadTime: 1751006386604
      items: 0 items
      protoLogs: 1 logs
    
    === Proto Logs Details ===
    
    Proto Log #1:
    {
      "frontend_log_event_id": "15cd988b-55bc-4a97-9e0b-05f6981a8487",
      "context": {
        "client_context": {
          "timestamp_millis": 1751006386604,
          "user_agent": "PyDatabricksSqlConnector/4.0.5"
        }
      },
      "entry": {
        "sql_driver_log": {
          "system_configuration": {
            "driver_version": "4.0.5",
            "os_name": "Darwin",
            "os_version": "24.5.0",
            "os_arch": "arm64",
            "runtime_name": "Python 3.11.13",
            "runtime_version": "3.11.13",
            "runtime_vendor": "CPython",
            "driver_name": "Databricks SQL Python Connector",
            "char_set_encoding": "utf-8",
            "locale_name": "en_US"
          },
          "driver_connection_params": {
            "http_path": <HTTP_PATH>,
            "mode": "THRIFT",
            "host_info": {
              "host_url": <SERVER_HOSTNAME>,
              "port": 443
            }
          },
          "error_info": {
            "error_name": "ConnectionError",
            "stack_trace": "Failed to establish connection: Error during request to server: : Invalid access token.. "
          }
        }
      }
    }
    
    === Response Details ===
    Status Code: 200
    
    Response Body:
    {
      "errors": [],
      "numSuccess": 0,
      "numProtoSuccess": 1,
      "numRealtimeSuccess": 0
    }
  

• N/A

Related Tickets & Documents

PECOBLR-636

[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).

[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).

[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).