Skip to content

Commit a1904b6

Browse files
committed
Resolving warnings and errors
1 parent 84b34f7 commit a1904b6

File tree

1 file changed

+10
-10
lines changed

1 file changed

+10
-10
lines changed

articles/azure-monitor/includes/azure-monitor-app-insights-opentelemetry-support.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ The Azure Monitor Exporter uses EventSource for its internal logging. The export
1616

1717
#### Step 2: Test connectivity between your application host and the ingestion service
1818

19-
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](../investigate-missing-telemetry.md).
19+
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry).
2020

2121
#### Known issues
2222

@@ -34,7 +34,7 @@ The Azure Monitor Exporter uses EventSource for its internal logging. The export
3434

3535
#### Step 2: Test connectivity between your application host and the ingestion service
3636

37-
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](../investigate-missing-telemetry.md).
37+
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry).
3838

3939
#### Known issues
4040

@@ -48,11 +48,11 @@ The following items are known issues for the Azure Monitor OpenTelemetry Exporte
4848

4949
#### Step 1: Enable diagnostic logging
5050

51-
By default, diagnostic logging is enabled in Azure Monitor Application Insights. For more information, see [Troubleshoot guide: Azure Monitor Application Insights for Java](java-standalone-troubleshoot.md).
51+
By default, diagnostic logging is enabled in Azure Monitor Application Insights. For more information, see [Troubleshoot guide: Azure Monitor Application Insights for Java](/troubleshoot/azure/azure-monitor/app-insights/telemetry/java-standalone-troubleshoot).
5252

5353
#### Step 2: Test connectivity between your application host and the ingestion service
5454

55-
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](../investigate-missing-telemetry.md).
55+
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry).
5656

5757
#### Known issues
5858

@@ -95,8 +95,10 @@ docker run -e APPLICATIONINSIGHTS_SELF_DIAGNOSTICS_LEVEL=DEBUG <image-name>
9595

9696
> [!NOTE]
9797
> Replace *`<image-name>`* with the docker image name accordingly.
98-
>
99-
[!INCLUDE [Third-party disclaimer](../../../../includes/third-party-disclaimer.md)]
98+
99+
**Third-party information disclaimer**
100+
101+
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
100102

101103
### [Node.js](#tab/nodejs)
102104

@@ -115,7 +117,7 @@ provider.register();
115117

116118
#### Step 2: Test connectivity between your application host and the ingestion service
117119

118-
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](../investigate-missing-telemetry.md).
120+
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry).
119121

120122
#### Known issues
121123

@@ -151,7 +153,7 @@ logger.addHandler(stream)
151153

152154
#### Step 2: Test connectivity between your application host and the ingestion service
153155

154-
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](../investigate-missing-telemetry.md).
156+
Application Insights SDKs and agents send telemetry to get ingested as REST calls at our ingestion endpoints. To test connectivity from your web server or application host computer to the ingestion service endpoints, use cURL commands or raw REST requests from PowerShell. For more information, see [Troubleshoot missing application telemetry in Azure Monitor Application Insights](/troubleshoot/azure/azure-monitor/app-insights/telemetry/investigate-missing-telemetry).
155157

156158
#### Step 3: Avoid duplicate telemetry
157159

@@ -222,8 +224,6 @@ app = Flask(__name__)
222224

223225
---
224226

225-
[!INCLUDE [Azure Help Support](/troubleshoot/includes/azure-help-support)]
226-
227227
## Support
228228

229229
Select a tab for the language of your choice to discover support options.

0 commit comments

Comments
 (0)