`configure_azure_monitor` attempts to use uninstalled libraries and logs tracebacks

[dylwil3]

• Package Name: azure-monitor-opentelemetry
• Package Version: 1.6.7
• Operating System:
• Python Version: 3.12

Describe the bug
configure_azure_monitor attempts to setup instrumentations for libraries that are not installed

To Reproduce
Steps to reproduce the behavior:

1. Install azure-monitor-opentelemetry without unnecessary dependencies (e.g. without django).
2. Run configure_azure_monitor

Observe logs like:

Exception occurred when instrumenting: django.
Traceback (most recent call last):
  File "/app/.venv/lib/python3.12/site-packages/azure/monitor/opentelemetry/_configure.py", line 222, in _setup_instrumentations
    instrumentor: BaseInstrumentor = entry_point.load()
                                     ^^^^^^^^^^^^^^^^^^

Expected behavior
No tracebacks displayed for attempts to setup instrumentation for uninstalled libraries.

Additional context
The problem seems to be in this function:

azure-sdk-for-python/sdk/monitor/azure-monitor-opentelemetry/azure/monitor/opentelemetry/_configure.py

Lines 210 to 214 in ce204aa

	def _setup_instrumentations(configurations: Dict[str, ConfigurationValue]):
	# entry_point_finder = _EntryPointDistFinder()
	# use pkg_resources for now until https://github.com/open-telemetry/opentelemetry-python/pull/3168 is merged
	for entry_point in entry_points(group="opentelemetry_instrumentor"):
	lib_name = entry_point.name

There used to be logic there for skipping setup on uninstalled libraries, but it was removed in #40463

[github-actions]

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @gulopesd @Haiying-MSFT @jairmyree @joshfree @KarishmaGhiya @KevinBlasko @kurtzeborn @nisha-bhatia @pvaneck @scottaddie @srnagar @ToddKingMSFT.

[jeremydvoss]

"There used to be logic there for skipping setup on uninstalled libraries, but it was removed"

Yes unfortunately there was a breaking change in OpenTelemetry. We adjusted for it in 1.6.7. However, it seems there are additional side effects of the breaking change that produce unnecessary logs. We are going to release a new version that pins the latest version of OTel <1.32/0.53b until the remaining breaking issues in the aforementioned breaking change are addressed.

[francogior]

While we wait for this to be fixed, you can avoid warnings by explictly disabling those that are not in use, for example:

configure_azure_monitor(
    # Assuming you are using fastapi
    instrumentation_options={
        "flask": {"enabled": False},
        "django": {"enabled": False},
        "psycopg2": {"enabled": False},
    },
    ...
)

[jeremydvoss]

Thanks @francogior

Alright, azure-monitor-opentelemetry==1.6.8 has been released and pins OTel dependencies to before the breaking change. Please try this latest version if you are having these issues.

In the meantime, we are working in the OTel community to fix the outcomes of the breaking change so that dependency conflicts are handled gracefully.