Azure resource providers

[zeitlinger]

Fixes #1214

Testing:

Has not been tested in a real setup yet - but all implementations are based on the existing resource providers in other languages.

Documentation:

done

Outstanding items

Owner

Need component owners. I can be one of them.

Host image attributes

VM seems to support host.image related attributes

• host.image.id =
• host.image.name =
• host.image.version =

(from https://learn.microsoft.com/en-us/azure/virtual-machines/instance-metadata-service?tabs=linux)

            "imageReference": {
                "id": "",
                "offer": "UbuntuServer",
                "publisher": "Canonical",
                "sku": "16.04.0-LTS",
                "version": "latest",
                "communityGalleryImageId": "/CommunityGalleries/testgallery/Images/1804Gen2/Versions/latest",
                "sharedGalleryImageId": "/SharedGalleries/1P/Images/gen2/Versions/latest",
                "exactVersion": "1.1686127202.30113"
            },

does that make sense?

Stop VM detector fast

Right now, the VM detector has a timeout of 1s - which means that it will block the startup process by 1s if we're not running in an Azure VM. How can we avoid that?

INFO: AzureVmResourceProvider.createResource took 1388 ms

An idea is to look for the /etc/resolv.conf file on linux - and some special registry key on windows.

Is that really the best option?

[zeitlinger]

@trask here's my first attempt - can you help with testing?

[heyams]

can we add aks (azure Kubernetes service)?

[heyams]

@zeitlinger do you think it's a good idea to add AKS?

cloud.provider=Azure
cloud.platform=azure_aks
cloud.resource_id=${armId},
cloud.region=${armRegion},
k8s.cluster.name=
k8s.namespace.name=
k8s.node.name=
k8s.pod.name=
k8s.pod.uid
k8s.container.name

k8s.deployment.name
k8s.deployment.uid

[zeitlinger]

yes, definitely. So far, I've started with the existing implementations in other languages.

Can you point me to a starting point to implement an AKS provider?

[zeitlinger]

@trask can you check?

[breedx-splk]

This seems good to me, once we get the component owners dialed in. Nice to have some vendor coverage.

[zeitlinger]

@breedx-splk please check again

[breedx-splk]

What's the motivation in copying instead of depending?

[zeitlinger]

it's a policy that library instrumentation must not depend on incubating libraries - all other contrib modules do that too

[breedx-splk]

@breedx-splk please check again

Still looking good to me....though it would have been nice not to have a bunch of extra new additional code to review after an approval. 😅

[zeitlinger]

@breedx-splk please check again

Still looking good to me....though it would have been nice not to have a bunch of extra new additional code to review after an approval. 😅

sorry - the PR was created before the new semconv policy - didn't spot that before

[zeitlinger]

@breedx-splk should work now