-
Notifications
You must be signed in to change notification settings - Fork 2.8k
[datadogexporter] Improve support of semantic conventions for K8s, Azure and ECS #2623
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
[datadogexporter] Improve support of semantic conventions for K8s, Azure and ECS #2623
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2623 +/- ##
==========================================
+ Coverage 91.30% 91.32% +0.02%
==========================================
Files 429 430 +1
Lines 21457 21492 +35
==========================================
+ Hits 19591 19628 +37
+ Misses 1396 1395 -1
+ Partials 470 469 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
…mo/app (open-telemetry#2623) Signed-off-by: Bogdan Drutu <[email protected]>
It would conflict with the ECS hostname
if ok && cloudProvider.StringVal() == conventions.AttributeCloudProviderAzure { | ||
return azure.ClusterNameFromAttributes(attrs) | ||
} else if ok && cloudProvider.StringVal() == conventions.AttributeCloudProviderAWS { | ||
return ec2.ClusterNameFromAttributes(attrs) | ||
} |
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.
I might not have followed everything here, is there a reason why we're not also doing this for GCP? Is it because there are no ways to get a cluster name from GCP-specific attributes?
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.
Yes, I should have mentioned it. There are none currently, there will be once #570 is resolved
Co-authored-by: Kylian Serrania <[email protected]>
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.
LGTM, left a comment to fix the codecov warning
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.
LGTM
This PR was marked stale due to lack of activity. It will be closed in 7 days. |
…ure and ECS (#2623) TL;DR: - Add support for the new Azure resource detector - Improve support for Kubernetes semantic conventions - Improve support for Kubernetes labels - Improve support for ECS semantic conventions ### Azure - The `host.id` (Azure VM ID) is sent as a host alias now, to replicate the Datadog Agent behavior. - The cluster name is taken from the resource group ID. ### ECS - Task family, cluster ARN and task revision are mapped to Datadog conventions. `container.id` priority to be taken as a hostname is lowered since we only want this as a last resort. ### Kubernetes - OpenTelemetry Kubernetes semantic conventions are mapped to Datadog conventions. - Kubernetes labels conventions (both Datadog-specific and general recommendations) are mapped to Datadog conventions. - We now take the Kubernetes cluster name on Azure (see above) and AWS.
Description:
TL;DR:
Azure
host.id
(Azure VM ID) is sent as a host alias now, to replicate the Datadog Agent behavior.ECS
container.id
priority to be taken as a hostname is lowered since we only want this as a last resort.Kubernetes
Link to tracking Issue: n/a
Testing: Added unit tests