Skip to content

Commit 2343c64

Browse files
Merge pull request #211771 from chcomley/users/chcomley/static-web-apps-ghi-91109-09-19-2022
GHI fix #91109 - added note with link to more info for client side telemetry
2 parents 1ca5dee + 272aaa7 commit 2343c64

File tree

1 file changed

+9
-7
lines changed

1 file changed

+9
-7
lines changed

articles/static-web-apps/monitor.md

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: Monitoring Azure Static Web Apps
2+
title: Monitor Azure Static Web Apps
33
description: Monitor requests, failures, and tracing information in Azure Static Web Apps
44
services: static-web-apps
55
author: craigshoemaker
66
ms.service: static-web-apps
77
ms.topic: conceptual
8-
ms.date: 4/23/2021
8+
ms.date: 09/19/2022
99
ms.author: cshoe
1010
---
1111

@@ -33,19 +33,21 @@ Use the following steps to add Application Insights monitoring to your static we
3333

3434
:::image type="content" source="media/monitoring/azure-static-web-apps-application-insights-add.png" alt-text="Add Application Insights to Azure Static Web Apps":::
3535

36+
Once you create the Application Insights instance, it creates an associated application setting in the Azure Static Web Apps instance used to link the services together.
37+
3638
> [!NOTE]
37-
> Once you create the Application Insights instance, an associated application setting is created in the Azure Static Web Apps instance used to link the services together.
39+
> If you want to track how the different features of your web app are used end-to-end client side, you can insert trace calls in your JavaScript code. For more information, see [Application Insights for webpages](/azure-monitor/app/javascript?tabs=snippet).
3840
3941
## Access data
4042

4143
1. From the _Overview_ window in your static web app, select the link next to the _Resource group_.
4244

4345
1. From the list, select the Application Insights instance prefixed with the same name as your static web app.
4446

45-
The following highlights a few locations in the portal used to inspect aspects of your application's API endpoints.
47+
The following table highlights a few locations in the portal you can use to inspect aspects of your application's API endpoints.
4648

4749
> [!NOTE]
48-
> For more detail on Application Insights usage, refer to [Application Insights overview](../azure-monitor/app/app-insights-overview.md).
50+
> For more information on Application Insights usage, see the [App insights overview](../azure-monitor/app/app-insights-overview.md).
4951
5052
| Type | Menu location | Description |
5153
|--- | --- | --- |
@@ -72,7 +74,7 @@ Using the following steps to view traces in your application.
7274

7375
## Limit logging
7476

75-
In some cases you may want to limit logging while still capturing details on errors and warnings by making the following changes to your _host.json_ file of the Azure Functions app.
77+
In some cases, you may want to limit logging while still capturing details on errors and warnings. You can do so by making the following changes to your _host.json_ file of the Azure Functions app.
7678

7779
```json
7880
{
@@ -94,4 +96,4 @@ In some cases you may want to limit logging while still capturing details on err
9496
## Next steps
9597

9698
> [!div class="nextstepaction"]
97-
> [Setup authentication and authorization](authentication-authorization.md)
99+
> [Set up authentication and authorization](authentication-authorization.md)

0 commit comments

Comments
 (0)