-
Notifications
You must be signed in to change notification settings - Fork 260
feat: create new telemetry handle that supports connection strings #3729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR introduces a new telemetry client that supports connection strings for initializing Application Insights telemetry, along with corresponding tests.
- Updated go.mod to replace the ApplicationInsights-Go dependency.
- Added a new function, NewAITelemetryWithConnectionString, in telemetrywrapper.go to enable connection string based initialization.
- Expanded tests in telemetrywrapper_test.go to cover the new connection string initialization.
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| go.mod | Updated ApplicationInsights-Go dependency replacement. |
| aitelemetry/telemetrywrapper_test.go | Added tests for connection string initialization and error checks. |
| aitelemetry/telemetrywrapper.go | Added NewAITelemetryWithConnectionString function implementation. |
Comments suppressed due to low confidence (1)
aitelemetry/telemetrywrapper_test.go:93
- There is a spelling mistake in the error message; 'intializing' should be changed to 'initializing'.
t.Errorf("Error intializing AI telemetry:%v", err)
987145b to
fa88a0b
Compare
|
This pull request is stale because it has been open for 2 weeks with no activity. Remove stale label or comment or this will be closed in 7 days |
132ce87 to
88d5717
Compare
|
@BeegiiK I'm not interested in maintaining a soft AppInsights fork. Have you talked to the owner of the repo to see if they would take this contribution? |
3fa5448 to
ebec4dd
Compare
1879644 to
127c175
Compare
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run NPM Scale Test |
|
Azure Pipelines successfully started running 1 pipeline(s). |
850849a to
8ed839f
Compare
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
c8facc2 to
16ec957
Compare
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…zure#3729) * feat: create new telemetry handle with connection strings * feat: Add application insights source code and remove dependency * feat: Create connection string helper function and update telemetry handle * feat: Polishing * feat: Address PR comments * feat: Update test telemetry handle initialization * feat: Re-initialise telemetry handles to fix race conditions during test execution * feat: revert string formatting changes * feat: fix lint
…3729) * feat: create new telemetry handle with connection strings * feat: Add application insights source code and remove dependency * feat: Create connection string helper function and update telemetry handle * feat: Polishing * feat: Address PR comments * feat: Update test telemetry handle initialization * feat: Re-initialise telemetry handles to fix race conditions during test execution * feat: revert string formatting changes * feat: fix lint
Reason for Change:
Currently, the telemetry handle can only work with instrumentation keys. If we want to use application insights in sovereign clouds, this would simply fail as the logging is shipped to a default ingestion endpoint and the
isPublicEnvironmentcheck.This PR introduces a new telemetry handle method that takes in a connection string, parses it, updates the configuration appropriately and initializes the new handle
Tested manually by updating DNC to use the new telemetry handle and verified that the logs were shipped to Kusto, with the connection string of the test application insights resource
Issue Fixed:
#3730
Requirements:
Notes: