Hi,

We are trying to remove or reduce our Application Insights DEPENDENCY logs.

Background: We have a DXP hosted instance of EpiServer. Our custom log entries only appear in application insights intermittently, this seems to be down to throttling and downsampling due to the sheer volume of entries. The biggest culprit seem to be the  DEPENDENCY type logs i.e. our mostly idle dev instance has 355K of these log entries per day, and our prod instance has about 1.05M per day. Most of these are meaningless SQL command logs. 

Things we have tried so far:

• We've edited the ApplicationInsights.config and removed HttpDependenciesParsingTelemetryInitializer from the TelemetryInitializers
• We've edited the ApplicationInsights.config and removed DependencyTrackingTelemetryModule from the TelemetryModules
• We've created a custom ITelemetryProcessor as per https://learn.microsoft.com/en-us/azure/azure-monitor/app/api-filtering-sampling
        (I notice in the debugger that this only hits for Trace logs, but not the DEPENDENCY ones)
• We've completely removed the ApplicationInsights.config 
• We've completely removed all logging (i.e. Microsoft.ApplicationInsights, System.Diagnostics.DiagnosticSource, and Microsoft.AspNet.TelemetryCorrelation nuget packages) 
        (this removes all custom log entries. however the DEPENDENCY TCP SQL logs still remain!)

Any advise or suggestions of how to remove these DEPENDENCY logs from being logged would be appreciated

Thanks,
Ivan