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/availability-azure-functions.md
+7Lines changed: 7 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,7 @@ This article will cover how to create an Azure Function with TrackAvailability()
39
39
40
40
Copy the code below into the run.csx file (this will replace the pre-existing code). To do this, go into your Azure Functions application and select your timer trigger function on the left.
41
41
42
+
[!div class="mx-imgBorder"]
42
43

43
44
44
45
> [!NOTE]
@@ -138,6 +139,7 @@ On the right under view files, select **Add**. Call the new file **function.proj
@@ -158,14 +160,17 @@ To make sure everything is working, you can look at the graph in the Availabilit
158
160
> [!NOTE]
159
161
> If you implemented your own business logic in runAvailabilityTest.csx then you will see successful results like in the screenshots below, if you did not then you will see failed results.
160
162
163
+
[!div class="mx-imgBorder"]
161
164

162
165
163
166
When you set up your test using Azure Functions you will notice, that unlike using **Add test** in the Availability tab, the name of your test will not appear and you will not be able to interact with it. The results are visualized but you get a summary view instead of the same detailed view you get when you create an availability test via the portal.
164
167
165
168
To see the end-to-end transaction details, select **Successful** or **Failed** under drill into, then select a sample. You can also get to the end-to-end transaction details by selecting a data point on the graph.
166
169
170
+
[!div class="mx-imgBorder"]
167
171

If you ran everything as is (without adding business logic), then you will see that the test failed.
@@ -174,8 +179,10 @@ If you ran everything as is (without adding business logic), then you will see t
174
179
175
180
You can use Logs(analytics) to view you availability results, dependencies, and more. To learn more about Logs, visit [Log query overview](../../azure-monitor/log-query/log-query-overview.md).
0 commit comments