-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[chore] [exporter/azuremonitor] Incorporate SDK Version Tagging in Azure Monitor Exporter #28999
[chore] [exporter/azuremonitor] Incorporate SDK Version Tagging in Azure Monitor Exporter #28999
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.
LGMT, pinging code owner @pcwiese for review.
@songy23 Got approval from code owner. Could you please help merge this PR? |
👋 Marked as ready to merge. A maintainer will help merge this PR (I don't have permission) |
@open-telemetry/collector-contrib-approvers Could you please help merge this PR, got an approval from the code owner. |
…ure Monitor Exporter (open-telemetry#28999) **Description:** <Describe what has changed.> <!--Ex. Fixing a bug - Describe the bug and how this fixes the issue. Ex. Adding a feature - Explain what this achieves.--> This pull request enhances the Azure Monitor Exporter by tagging telemetry data with the OpenTelemetry Collector's internal SDK version. This additional metadata will facilitate improved monitoring, troubleshooting, and analysis of data sourced from different versions of the collector. **Changes:** - Added functionality in `azuremonitorexporter` to append the SDK version to each telemetry envelope. - Implemented `getCollectorVersion` to dynamically fetch the current version of the OpenTelemetry Collector. **Sample SDK Version String:** - The SDK version string is formatted as follows: `otelc-<version>-<os>-<arch>` - Example: `otelc-v0.88.1-lin-amd64` **Note:** - Since this change pertains to internal diagnostic data enrichment and does not modify any external behavior or configuration interfaces, it does not necessitate a changelog entry. **Link to tracking Issue:** <Issue number if applicable> **Testing:** <Describe what testing was performed and which tests were added.> - Adjusted existing unit tests to ensure the SDK version string is correctly included in the telemetry envelopes. ```json { "ver": 1, "name": "Microsoft.ApplicationInsights.RemoteDependency", "time": "2023-11-06T15:21:12.9807976-08:00", "sampleRate": 100, "seq": "", "iKey": "Ikey", "tags": { "ai.cloud.role": "otlp-test", "ai.cloud.roleInstance": "2c4a6d1b-f7cb-4579-8d05-65b83b4acf7e", *"ai.internal.sdkVersion": "otelc-v0.88.1-lin-amd64",* "ai.operation.id": "0e3a010cb64d919aa8f214bf0a166334", "ai.operation.parentId": "" }, "data": { } } ``` --------- Co-authored-by: Yang Song <[email protected]>
Description:
This pull request enhances the Azure Monitor Exporter by tagging telemetry data with the OpenTelemetry Collector's internal SDK version. This additional metadata will facilitate improved monitoring, troubleshooting, and analysis of data sourced from different versions of the collector.
Changes:
azuremonitorexporter
to append the SDK version to each telemetry envelope.getCollectorVersion
to dynamically fetch the current version of the OpenTelemetry Collector.Sample SDK Version String:
otelc-<version>-<os>-<arch>
otelc-v0.88.1-lin-amd64
Note:
Link to tracking Issue:
Testing: