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
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/api-custom-events-metrics.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -617,7 +617,7 @@ In Java, many dependency calls can be automatically tracked by using the
617
617
You use this call if you want to track calls that the automated tracking doesn't catch.
618
618
619
619
To turn off the standard dependency-tracking module in C#, edit [ApplicationInsights.config](./configuration-with-applicationinsights-config.md) and delete the reference to `DependencyCollector.DependencyTrackingTelemetryModule`. For Java, see
620
-
[Suppressing specific autocollected telemetry](./java-standalone-config.md#suppressing-specific-auto-collected-telemetry).
620
+
[Suppressing specific autocollected telemetry](./java-standalone-config.md#suppress-specific-auto-collected-telemetry).
Copy file name to clipboardExpand all lines: articles/azure-monitor/app/availability-overview.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,8 +16,8 @@ You can set up availability tests for any HTTP or HTTPS endpoint that's accessib
16
16
17
17
There are four types of availability tests:
18
18
19
-
*[URL ping test (classic)](monitor-web-app-availability.md): You can create this simple test through the portal to validate whether an endpoint is responding and measure performance associated with that response. You can also set custom success criteria coupled with more advanced features, like parsing dependent requests and allowing for retries.
20
-
*[Standard test](availability-standard-tests.md): This single request test is similar to the URL ping test. It includes SSL certificate validity, proactive lifetime check, HTTP request verb (for example `GET`, `HEAD`, or `POST`), custom headers, and custom data associated with your HTTP request.
19
+
*[URL ping test (classic)](monitor-web-app-availability.md): You can create this test through the Azure portal to validate whether an endpoint is responding and measure performance associated with that response. You can also set custom success criteria coupled with more advanced features, like parsing dependent requests and allowing for retries.
20
+
*[Standard test](availability-standard-tests.md): This single request test is similar to the URL ping test. It includes TLS/SSL certificate validity, proactive lifetime check, HTTP request verb (for example,`GET`, `HEAD`, or `POST`), custom headers, and custom data associated with your HTTP request.
21
21
*[Multi-step web test (classic)](availability-multistep.md): You can play back this recording of a sequence of web requests to test more complex scenarios. Multi-step web tests are created in Visual Studio Enterprise and uploaded to the portal, where you can run them.
22
22
*[Custom TrackAvailability test](availability-azure-functions.md): If you decide to create a custom application to run availability tests, you can use the [TrackAvailability()](/dotnet/api/microsoft.applicationinsights.telemetryclient.trackavailability) method to send the results to Application Insights.
23
23
@@ -27,7 +27,7 @@ There are four types of availability tests:
27
27
You can create up to 100 availability tests per Application Insights resource.
28
28
29
29
> [!NOTE]
30
-
> Availability tests are stored encrypted, according to [Microsoft Azure Data Encryption at rest](../../security/fundamentals/encryption-atrest.md#encryption-at-rest-in-microsoft-cloud-services) policies.
30
+
> Availability tests are stored encrypted, according to [Azure data encryption at rest](../../security/fundamentals/encryption-atrest.md#encryption-at-rest-in-microsoft-cloud-services) policies.
31
31
32
32
## Troubleshooting
33
33
@@ -37,7 +37,7 @@ See the dedicated [troubleshooting article](/troubleshoot/azure/azure-monitor/ap
37
37
38
38
*[Availability alerts](availability-alerts.md)
39
39
*[URL tests](monitor-web-app-availability.md)
40
-
*[Standard Tests](availability-standard-tests.md)
40
+
*[Standard tests](availability-standard-tests.md)
41
41
*[Multi-step web tests](availability-multistep.md)
42
42
*[Create and run custom availability tests using Azure Functions](availability-azure-functions.md)
0 commit comments