[resourcedetectionprocessor] Azure resource detector #2326
Comments
tigrannajaryan
pushed a commit
that referenced
this issue
Mar 3, 2021
Create Azure resource detector for gathering metadata from the [Azure IMDS](https://aka.ms/azureimds). Due to Azure/azure-sdk-for-go#982 we have to query the endpoint manually. **Link to tracking Issue:** Fixes #2326 **Testing:** Added unit tests. Tested end to end with provided sample configuration on an Azure VM.
pmatyjasek-sumo
referenced
this issue
in pmatyjasek-sumo/opentelemetry-collector-contrib
Apr 28, 2021
Create Azure resource detector for gathering metadata from the [Azure IMDS](https://aka.ms/azureimds). Due to Azure/azure-sdk-for-go#982 we have to query the endpoint manually. **Link to tracking Issue:** Fixes #2326 **Testing:** Added unit tests. Tested end to end with provided sample configuration on an Azure VM.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The resource detection processor has support for gathering metadata from AWS and GCE cloud services. It would be useful to also have support for Azure metadata: there are already some Azure-specific semantic conventions on the specification and it would make sense to add a detector for this platform too.
Describe the solution you'd like
Similarly to other cloud providers, Azure has the Instance Metadata Service where one can query information about a certain VM.
A new detector,
azureis created to gather Azure VM instance metadata. Using the instance metadata the following fields could be set:cloud.providerset toazure(if the query is successful),cloud.account.id, the Azure subscription ID,cloud.regionand/orcloud.zone,host.id, the Azure VM ID,host.nameandhost.type.Describe alternatives you've considered
Create a new component only for Azure or query the endpoint directly from components that need it.
The text was updated successfully, but these errors were encountered: