Skip to content

Commit a453c7f

Browse files
committed
[AppInsights][AaronMax] removing duplicate important notice
1 parent afc96a2 commit a453c7f

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

articles/azure-monitor/app/asp-net-troubleshoot-no-data.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,6 @@ ms.date: 05/21/2020
1111

1212
[!INCLUDE [azure-monitor-log-analytics-rebrand](../../../includes/azure-monitor-instrumentation-key-deprecation.md)]
1313

14-
1514
## Some of my telemetry is missing
1615
*In Application Insights, I only see a fraction of the events that are being generated by my app.*
1716

@@ -41,10 +40,6 @@ Internet Information Services (IIS) logs counts of all request reaching IIS and
4140

4241
* See [Troubleshooting Status Monitor](./status-monitor-v2-troubleshoot.md).
4342

44-
> [!IMPORTANT]
45-
> [Connection Strings](./sdk-connection-string.md?tabs=net) are recommended over instrumentation keys. New Azure regions **require** the use of connection strings instead of instrumentation keys. Connection string identifies the resource that you want to associate your telemetry data with. It also allows you to modify the endpoints your resource will use as a destination for your telemetry. You will need to copy the connection string and add it to your application's code or to an environment variable.
46-
47-
4843
## <a id="SSL"></a>Check TLS/SSL client settings (ASP.NET)
4944

5045
If you have an ASP.NET application hosted in Azure App Service or in IIS on a virtual machine, your application could fail to connect to the Snapshot Debugger service due to a missing SSL security protocol.

0 commit comments

Comments
 (0)