Closed progxaker closed 3 months ago
@progxaker Thanks for your feedback! We will investigate and update as appropriate.
As asked, Cc @trask @jeanbisutti.
Thanks for your dedication to our documentation. This has been moved to an internal work item for triage and prioritization. Thanks in advance for your understanding as we investigate to provide the most accurate documentation updates. #please-close
Internal work item: https://dev.azure.com/msft-skilling/Content/_workitems/edit/218340
Our support team is available to assist you if you have any pressing questions or problems that need to be resolved. You can create a support ticket by visiting the following link: https://azure.microsoft.com/support/create-ticket/
Hello @AaronMaxwell. Are there plans to document this in the first half of the year?
It looks like this was added in https://github.com/MicrosoftDocs/azure-docs/commit/8918ba08ebb8c080455c03960e1f5da76417bf2a, but w/o applicationinsights.internal.methods.include
.
Hello @AaronMaxwell. Are there plans to document the parameter methods.include
?
Azure technology: Azure Monitor OpenTelemetry Distro Link to the article: https://learn.microsoft.com/en-us/azure/azure-monitor/app/java-standalone-config Description: the Application Insights development team renamed the default OpenTelemetry parameter (
otel.instrumentation.methods.include
) to their ownapplicationinsights.internal.methods.include
without documenting this anywhere in the Azure Learn portal.I asked Trask about this, and he gave a link to the https://github.com/microsoft/ApplicationInsights-Java/issues/2048#issuecomment-1179418344 where he added
preview.customInstrumentation[]
and gave a little note about it, but this is also undocumented.To clarify and track this beyond just within the product team, I'm creating this issue.
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.