Good point, an extra HTTP request is made, but not always:

• most of the azure resource providers are only executed when some environment variables are set
• the one that does an http call is executed last, as we can see in AzureVmResourceProvider implementation.
• in the case where none is relevant, the "expensive" one will be systematically executed, which is similar to what the EC2 resource provider does for AWS, as there is no easy and fast way to do that, there are "hack-ish" ways using dmidecode but those require root privileges so an http request isn't that bad after all.

So yes, it might make the app startup slightly slower, at the expense of a better out of the box experience. If that becomes an issue we can provide a dedicated documentation to optimize application overhead and startup time.

Let's add a startup time section in the doc, we know from experience that it's important for some customers

@jackshirazi I've opened elastic/opentelemetry#193 for that, it anticipates the availability of the feature in EDOT Java, which in fact depends on :

• instrumentation java next release (likely due within about a week)
• update the upstream dependency in this repo (should be an automatic dependency update PR)
• do a release of EDOT Java