Locate the "Sitecore.Cloud.ApplicationInsights.config" in your \App-Config\Include\zzz folder, and disable it by adding ".disabled" to the end of the filename.
In your "ConnectionString.config" file found in \App_Config, remove the connection string for the AI instrumentation.
Correct. Client side telemetry is normally part of layouts which are supplied with the website. Sitecore does not yet implement client-side telemetry, but we may implement relevant renderings in the future.
We have not tested Sitecore with Application Insights Profiler, and this is an experimental feature, so it should only be enabled during profiling ...
I never seen a list with usefull metrics. I discussed with Azure Team few months ago and they mention me to disabled GetChangesAvgTime counter.
One specific counter, GetChangesAvgTime, logged multiple times a second that can be disabled. It is related to change tracking on XDB search index worker.
To disable this specific counter please follow next steps: ...
This is because Sitecore includes it's own (old) version of log4net in the Sitecore.Logging assembly.
Bas Lijten has written a blog post about this and how to extend the Sitecore logging.
Here's part of his summary at the end:
The default Sitecore implementation of log4net is not optimal, the implementation is outdated and doesn’t support 3rd party add-...
While not the answer to breaking down logging each rendering, It's quite possible to change the GET Sitecore/Index to show its correct url.
You need to implement a custom telemetry processor, looking at the request item and updating both the Name properties of the request item as well as for the Operation. Operation Name is what you see Azure Portal.
Just expanding on Vlad's answer in light of new information - in Sitecore 9.1.0 they have removed a fair few counters. In comparison with 9.0.2 they have removed:
228, 229, 232, 233, 270 to 275
2118 - 2121
However they have added a few dozen too here.