You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Microsoft.ApplicationInsights.NLogTarget only supports an instrumentation key. This limits its functionality such that it can only target App Insights in Azure commercial. Also, instrumentation key only configuration is being deprecated (link).
Can connection string support be added to the configuration section of Microsoft.ApplicationInsights.NLogTarget? Below is the current layout of the config in XML form. Could connectionString be an optional element alongside instrumentationKey?
<extensions>
<add assembly="Microsoft.ApplicationInsights.NLogTarget" />
</extensions>
<targets>
<target xsi:type="ApplicationInsightsTarget" name="aiTarget">
<instrumentationKey>Your_Resource_Key</instrumentationKey> <!-- Only required if not using ApplicationInsights.config -->
<contextproperty name="threadid" layout="${threadid}" /> <!-- Can be repeated with more context -->
</target>
</targets>
<rules>
<logger name="*" minlevel="Trace" writeTo="aiTarget" />
</rules>
Thank you.
The text was updated successfully, but these errors were encountered:
This issue is stale because it has been open 300 days with no activity. Remove stale label or this will be closed in 7 days. Commenting will instruct the bot to automatically remove the label.
Currently the Microsoft.ApplicationInsights.NLogTarget only supports an instrumentation key. This limits its functionality such that it can only target App Insights in Azure commercial. Also, instrumentation key only configuration is being deprecated (link).
Can connection string support be added to the configuration section of Microsoft.ApplicationInsights.NLogTarget? Below is the current layout of the config in XML form. Could connectionString be an optional element alongside instrumentationKey?
Thank you.
The text was updated successfully, but these errors were encountered: