feat: enable operational telemetry #539
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
We need to begin sending operational telemetry for users of our runtime. Telemetry sharing is disabled by default when no configuration is specified.
Solution
Testing
Manually tested with "CodeWhisperer Agentic Server Token" extension in language-servers. Used
TELEMETRY_GATEWAY_ENDPOINT
to direct telemetry to a non-prod endpoint. Added 'telemetryOptOut' ininitializationOptions
in activation.ts file.Tested scenarios:
telemetryOptOut: true
- OpenTelemetry SDK is not initialized and telemetry is not exported to the backend.telemetryOptOut: false
- OpenTelemetry SDK logs appear at Debug level, indicating successful SDK initialization. Metrics are sent to the backend at the desired interval and are accepted in the expected format.telemetryOptOut
not specified - Results were the same astelemetryOptOut: true
.Additionally, confirmed that sending data to the actual prod telemetry endpoint works.
License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.