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
Use Azure File Sync to centralize your organization's file shares in Azure Files, while keeping the flexibility, performance, and compatibility of an on-premises file server. Azure File Sync transforms Windows Server into a quick cache of your Azure file share. You can use any protocol that's available on Windows Server to access your data locally, including SMB, NFS, and FTPS. You can have as many caches as you need across the world.
15
15
16
16
## Collect data with Azure Monitor
17
17
18
18
This table describes how you can collect data to monitor your service, and what you can do with the data once collected:
19
19
20
20
|Data to collect|Description|How to collect and route the data|Where to view the data|Supported data|
|Metric data|Metrics are numerical values that describe an aspect of a system at a particular point in time. Metrics can be aggregated using algorithms, compared to other metrics, and analyzed for trends over time.|- Collected automatically at regular intervals.</br> - You can route some platform metrics to a Log Analytics workspace to query with other data. Check the **DS export** setting for each metric to see if you can use a diagnostic setting to route the metric data.|[Metrics explorer](/azure/azure-monitor/essentials/metrics-getting-started)|[Azure File Sync metrics supported by Azure Monitor](monitor-file-sync-reference.md#metrics)|
23
-
|Resource log data|Logs are recorded system events with a timestamp. Logs can contain different types of data, and be structured or free-form text. You can route resource log data to Log Analytics workspaces for querying and analysis.|[Create a diagnostic setting](/azure/azure-monitor/essentials/create-diagnostic-settings) to collect and route resource log data.|[Log Analytics](/azure/azure-monitor/learn/quick-create-workspace)||
24
-
|Activity log data|The Azure Monitor activity log provides insight into subscription-level events. The activity log includes information like when a resource is modified or a virtual machine is started.|- Collected automatically.</br> - [Create a diagnostic setting](/azure/azure-monitor/essentials/create-diagnostic-settings) to a Log Analytics workspace at no charge.|[Activity log](/azure/azure-monitor/essentials/activity-log)||
22
+
|Metric data|Metrics are numerical values that describe an aspect of a system at a particular point in time. Metrics can be aggregated using algorithms, compared to other metrics, and analyzed for trends over time.|Collected automatically at regular intervals. |[Metrics explorer](/azure/azure-monitor/essentials/metrics-getting-started)|[Azure File Sync metrics supported by Azure Monitor](monitor-file-sync-reference.md#metrics)|
23
+
|Activity log data|The Azure Monitor activity log provides insight into subscription-level events. The activity log includes information like when a resource is modified or a virtual machine is started.|Collected automatically.|[Activity log](/azure/azure-monitor/essentials/activity-log)||
For the list of all of the metrics data supported by Azure Monitor, see [Azure Monitor supported metrics](/azure/azure-monitor/platform/metrics-supported).
27
26
28
27
## Built in monitoring for Azure File Sync
29
28
29
+
This article describes how to monitor your Azure File Sync deployment by using Azure Monitor, Storage Sync Service, and Windows Server. It covers the following scenarios:
30
+
31
+
- View Azure File Sync metrics in Azure Monitor.
32
+
- Create alerts in Azure Monitor to proactively notify you of critical conditions.
33
+
- View health of your Azure File Sync deployment using the Azure portal.
34
+
- Use the event logs and performance counters on Windows Server to monitor the health of your Azure File Sync deployment.
35
+
36
+
### View Azure File Sync metrics
37
+
38
+
Metrics for Azure File Sync are enabled by default and are sent to Azure Monitor every 15 minutes.
39
+
40
+
To view Azure File Sync metrics in Azure Monitor:
41
+
42
+
1. Go to your **Storage Sync Service** in the **Azure portal** and select **Metrics**.
43
+
1. Select the **Metric** drop-down and select the metric you want to view.
44
+
45
+
:::image type="content" source="media/storage-sync-files-troubleshoot/file-sync-metrics.png" alt-text="Screenshot of Azure File Sync metrics in the Azure portal.":::
46
+
47
+
Alerts proactively notify you when important conditions are found in your monitoring data. To learn more about configuring alerts in Azure Monitor, see [Overview of alerts in Microsoft Azure](/azure/azure-monitor/alerts/alerts-overview).
48
+
49
+
### Alerts
50
+
51
+
To create alerts for Azure File Sync:
52
+
53
+
1. Go to your **Storage Sync Service** in the **Azure portal**.
54
+
2. Select **Alerts** in the Monitoring section and then select **+ New alert rule**.
55
+
3. Select **Select condition** and provide the following information for the alert:
56
+
-**Metric**
57
+
-**Dimension name**
58
+
-**Alert logic**
59
+
4. Select **Select action group** and add an action group (email, SMS, etc.) to the alert either by selecting an existing action group or creating a new action group.
60
+
5. Fill in the **Alert details** like **Alert rule name**, **Description**, and **Severity**.
61
+
6. Select **Create alert rule** to create the alert.
62
+
63
+
> [!NOTE]
64
+
> If you configure an alert using the Server Name dimension and the server is renamed, the alert will need to be updated to monitor the new server name.
65
+
66
+
### Storage Sync Service
67
+
30
68
To view the health of your Azure File Sync deployment in the **Azure portal**, navigate to the **Storage Sync Service**. The following information is available:
31
69
32
70
- Registered server health
@@ -41,7 +79,7 @@ To view the health of your Azure File Sync deployment in the **Azure portal**, n
41
79
42
80
- Metrics
43
81
44
-
### Registered server health
82
+
####Registered server health
45
83
46
84
To view the **registered server health** in the portal, navigate to the **Registered servers** section of the **Storage Sync Service**.
47
85
@@ -50,7 +88,7 @@ To view the **registered server health** in the portal, navigate to the **Regist
50
88
- If the **Registered server** state is **Online**, the server is successfully communicating with the service.
51
89
- If the **Registered server** state is **Appears Offline**, the Storage Sync Monitor process (AzureStorageSyncMonitor.exe) isn't running or the server is unable to access the Azure File Sync service. For more information, see the [troubleshooting documentation](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-group-management?toc=/azure/storage/file-sync/toc.json#server-endpoint-noactivity).
52
90
53
-
### Server endpoint health
91
+
####Server endpoint health
54
92
55
93
To view the health of a **server endpoint** in the portal, navigate to the **Sync groups** section of the **Storage Sync Service** and select a **sync group**.
56
94
@@ -61,7 +99,7 @@ To view the health of a **server endpoint** in the portal, navigate to the **Syn
61
99
- The **Cloud tiering space savings** provides the amount of disk space saved by cloud tiering. The data provided for **Cloud tiering space savings** is based on Event ID 9071 that is logged in the Telemetry event log at the server. To view other cloud tiering information and metrics, go to the **Server Endpoint Properties** and navigate to the **Cloud tiering status** section. To learn more, see [Monitor cloud tiering](file-sync-monitor-cloud-tiering.md).
62
100
- To view **Tiering errors** and **Recall errors** in the portal, go to the **Server Endpoint Properties** and navigate to the **Errors + troubleshooting** section. **Tiering errors** is based on Event ID 9003 that is logged in the Telemetry event log at the server and **Recall errors** is based on Event ID 9006. For more information about files that fail to tier or recall, see [How to troubleshoot files that fail to tier](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-cloud-tiering?toc=/azure/storage/file-sync/toc.json#how-to-troubleshoot-files-that-fail-to-tier) and [How to troubleshoot files that fail to be recalled](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-cloud-tiering?toc=/azure/storage/file-sync/toc.json#how-to-troubleshoot-files-that-fail-to-be-recalled).
63
101
64
-
### Metric charts
102
+
####Metric charts
65
103
66
104
The following metric charts are viewable in the Storage Sync Service portal:
67
105
@@ -97,7 +135,7 @@ To monitor registered server, sync, and cloud tiering health, use the Telemetry
97
135
98
136
- Event ID 9121 is logged for each per-item error once the sync session completes. Use this event to determine the number of files that are failing to sync with this error (**PersistentCount** and **TransientCount**). You should investigate persistent per-item errors. For more information, see [How do I see if there are specific files or folders that aren't syncing?](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#how-do-i-see-if-there-are-specific-files-or-folders-that-are-not-syncing).
99
137
100
-
- Event ID 9302 is logged every 5 to 10 minutes if there's an active sync session. Use this event to determine how many items are to be synced (**TotalItemCount**), number of items that synced so far (**AppliedItemCount**) and number of items that failed to sync due to a per-item error (**PerItemErrorCount**). If sync isn't making progress (**AppliedItemCount=0**), the sync session eventually fails and an Event ID 9102 will be logged with the error. For more information, see the [sync progress documentation](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#how-do-i-monitor-the-progress-of-a-current-sync-session).
138
+
- Event ID 9302 is logged every 5 to 10 minutes if there's an active sync session. Use this event to determine how many items are to be synced (**TotalItemCount**), number of items that synced so far (**AppliedItemCount**) and number of items that failed to sync due to a per-item error (**PerItemErrorCount**). If sync isn't making progress (**AppliedItemCount=0**), the sync session eventually fails and an Event ID 9102 is logged with the error. For more information, see the [sync progress documentation](/troubleshoot/azure/azure-storage/file-sync-troubleshoot-sync-errors?toc=/azure/storage/file-sync/toc.json#how-do-i-monitor-the-progress-of-a-current-sync-session).
101
139
102
140
- Registered server health
103
141
@@ -140,8 +178,6 @@ The following performance counters for Azure File Sync are available in Performa
Metrics for Azure File Sync are enabled by default and are sent to Azure Monitor every 15 minutes.
29
-
30
-
To view Azure File Sync metrics in Azure Monitor:
31
-
32
-
1. Go to your **Storage Sync Service** in the **Azure portal** and select **Metrics**.
33
-
1. Select the **Metric** drop-down and select the metric you want to view.
34
-
35
-
:::image type="content" source="media/storage-sync-files-troubleshoot/file-sync-metrics.png" alt-text="Screenshot of Azure File Sync metrics in the Azure portal.":::
0 commit comments