Skip to content

Commit 2a71378

Browse files
committed
App Insights Az Functions: Fixing non-blocking issue
1 parent 1b7ad61 commit 2a71378

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ ms.author: mogrobin
1818
This article will cover how to create an Azure Function with TrackAvailability() that will run periodically according to the configuration given in TimerTrigger function. The results of this test will be sent to your Application Insights resource, where you will be able to query for and alert on the availability results data. This allows you to create customized tests similar to what you can do via [Availability Monitoring](../../azure-monitor/app/monitor-web-app-availability.md) in the portal. Customized tests will allow you to write more complex availability tests than is possible using the portal UI, monitor an app inside of your Azure VNET, change the endpoint address, or create an availability test even if this feature is not available in your region.
1919

2020

21-
## Create Timer triggered function
21+
## Create timer triggered function
2222

2323
- If you have an Application Insights Resource:
2424
- By default Azure Functions creates an Application Insights resource but if you would like to use one of your already created resources you will need to specify that during creation.
@@ -36,7 +36,7 @@ This article will cover how to create an Azure Function with TrackAvailability()
3636
- By default when you are creating your Azure Functions application it will create an Application Insights resource for you.
3737
- Follow the instructions on how to [create an Azure Functions resource and Timer triggered function](https://docs.microsoft.com/azure/azure-functions/functions-create-scheduled-function) (stop before clean-up).
3838

39-
## Sample Code
39+
## Sample code
4040

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

@@ -195,7 +195,7 @@ On the right under view files, select **Add**. Call the new file **function.proj
195195

196196
![On the right select, add. Name the file function.proj](media/availability-azure-functions/addfile.png)
197197

198-
## Check Availability
198+
## Check availability
199199

200200
To make sure everything is working, you can look at the graph in the Availability tab of your Application Insights resource.
201201

@@ -209,15 +209,15 @@ To see the end-to-end transaction details, select **Successful** or **Failed** u
209209

210210
![End-to-end transaction details](media/availability-azure-functions/end-to-end.png)
211211

212-
## Query in Logs(Analytics)
212+
## Query in Logs (Analytics)
213213

214214
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).
215215

216216
![Availability results](media/availability-azure-functions/availabilityresults.png)
217217

218218
![Dependencies](media/availability-azure-functions/dependencies.png)
219219

220-
## Next Steps
220+
## Next steps
221221

222222
- [Application Map](../../azure-monitor/app/app-map.md)
223223
- [Transaction diagnostics](../../azure-monitor/app/transaction-diagnostics.md)

0 commit comments

Comments
 (0)