Skip to content

Commit 97ffaad

Browse files
committed
fixing screenshots
1 parent bf519b0 commit 97ffaad

File tree

8 files changed

+7
-0
lines changed

8 files changed

+7
-0
lines changed

articles/azure-monitor/app/availability-azure-functions.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,6 +39,7 @@ This article will cover how to create an Azure Function with TrackAvailability()
3939

4040
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.
4141

42+
[!div class="mx-imgBorder"]
4243
![Azure function's run.csx in Azure portal](media/availability-azure-functions/runcsx.png)
4344

4445
> [!NOTE]
@@ -138,6 +139,7 @@ On the right under view files, select **Add**. Call the new file **function.proj
138139

139140
```
140141

142+
[!div class="mx-imgBorder"]
141143
![On the right select, add. Name the file function.proj](media/availability-azure-functions/addfile.png)
142144

143145
On the right under view files, select **Add**. Call the new file **runAvailabilityTest.csx** with the following configuration.
@@ -158,14 +160,17 @@ To make sure everything is working, you can look at the graph in the Availabilit
158160
> [!NOTE]
159161
> 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.
160162
163+
[!div class="mx-imgBorder"]
161164
![Availability tab with successful results](media/availability-azure-functions/availtab.png)
162165

163166
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.
164167

165168
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.
166169

170+
[!div class="mx-imgBorder"]
167171
![Select a sample availability test](media/availability-azure-functions/sample.png)
168172

173+
[!div class="mx-imgBorder"]
169174
![End-to-end transaction details](media/availability-azure-functions/end-to-end.png)
170175

171176
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
174179

175180
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).
176181

182+
[!div class="mx-imgBorder"]
177183
![Availability results](media/availability-azure-functions/availabilityresults.png)
178184

185+
[!div class="mx-imgBorder"]
179186
![Dependencies](media/availability-azure-functions/dependencies.png)
180187

181188
## Next steps
154 KB
Loading
33.4 KB
Loading
50.3 KB
Loading
35.9 KB
Loading
47.3 KB
Loading
53 KB
Loading
11.5 KB
Loading

0 commit comments

Comments
 (0)