Azure Data Explorer Exporter permanently fails on init due to lack of retries in dependency

[ben-childs-docusign]

Component(s)

exporter/azuredataexplorer

What happened?

Description

When using the azure data explorer exporter on a machine with a flaky network (in this case it was a windows container which was seeing network issues on launch), I saw the data explorer fail permanently due to a failed network call during initialization which gets memoized and never retried.

Steps to Reproduce

Try to init azure data explorer exporter in an environment with flaky network.

Expected Result

The init eventually succeeds

Actual Result

The exporter gets stuck in a permanent failed state due to memoization in the azure-kusto-go component

Collector version

v0.77.0

Environment information

Environment

OS: Windows 2019
Compiler(if manually compiled): go 1.19.8

OpenTelemetry Collector configuration

No response

Log output

Kind(KInternal): Error while getting token : Get \"https://****.eastus.kusto.windows.net/v1/rest/auth/metadata\": net/http: TLS handshake timeout

Additional context

This issue was logged in azure-kusto-go and fixed in 0.13.1
Azure/azure-kusto-go#188

I have tested the fix locally and confirmed the issue is resolved.

[github-actions]

Pinging code owners:

• exporter/azuredataexplorer: @asaharan @ag-ramachandran

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[ag-ramachandran]

Hello @ben-childs-docusign, Thanks for reporting the issue, will have a look at this.
Will try out a way if there can be retries initiated in case of network flakiness. Will keep this issue posted based on internal discussions we have.

[ag-ramachandran]

Hello @codeboten , @mx-psi. We've made a small PR:: #22933 with the SDK update and fix of all deprecations related to that. Kindly review when you get a chance!