Add azure_monitor to metrics exporter for AKS

[xiang17]

Fix # .

If APPLICATIONINSIGHTS_METRICS_TO_LOGANALYTICS_ENABLED is set to true, send OTel metrics to Breeze even if OTEL_METRICS_EXPORTER doesn't have azure_monitor.

For significant contributions please make sure you have completed the following items:

• Design discussion issue #
• Changes in public surface reviewed
• CHANGELOG.md updated

[jeanbisutti]

The specifications seem to indicate that the APPLICATIONINSIGHTS_METRICS_TO_LOGANALYTICS_ENABLED should only be used in case of AKS and Auto-Attach. AKS detection can be done in this way:

ApplicationInsights-Java/agent/agent-tooling/src/main/java/com/microsoft/applicationinsights/agent/internal/diagnostics/DiagnosticsHelper.java

Line 55 in 25f901b

} else if (!Strings.isNullOrEmpty(System.getenv("AKS_ARM_NAMESPACE_ID"))) {

Auto-Attach detection requires the Java agent JAR path . See DiagnosticHelper.initRpIntegration.(Path agentPath) and DiagnosticsHelper.setRpAttachType(Path agentPath, String markerFile) .

AiConfigCustomizer is instanciated in the SecondEntry point:

ApplicationInsights-Java/agent/agent-tooling/src/main/java/com/microsoft/applicationinsights/agent/internal/init/SecondEntryPoint.java

Line 266 in 25f901b

.addPropertiesCustomizer(new AiConfigCustomizer())

The RP integration of DiagnosticsHelper is initiliazed in the first entry point:

ApplicationInsights-Java/agent/agent-tooling/src/main/java/com/microsoft/applicationinsights/agent/internal/init/FirstEntryPoint.java

Line 92 in 25f901b

DiagnosticsHelper.initRpIntegration(agentPath);

I am not sure that the first entry point always finishes to execute before the second one. If the first entry point always finishes to execute before the second one, you could use the RP initialization done in the first entry point from the second one. Otherwise, you could reimplement the same kind of things in the second entry point.