Monitoring file share health states, lifecycle status, and events
By using the console, the CLI, or the API, you can check on the status and health states of the file shares.
Replication sync health
Replication is an asynchronous operation, which is not instantaneous. The system queries the last sync status every 15 minutes. The result shows the data of the last replication that completed, such as start and end date, and the transferred data volume.
You can see information about the last replication operation when you view the details of either the source or the replica share. For more information, see View details of a file share in the UI.
You can see information about the last replication operation when you list the details of either the source or the replica share. For more information, see View details of a file share from the CLI.
You can programmatically retrieve the last sync details by calling the /shares
method in the VPC API. Look for the latest_sync
section in
the API response to see when the replication started (started_at
), when it ended (completed_at
), and how much data was transferred (data_transferred
). For more information, see View a single file share with the API.
When the amount of data to be transferred exceeds the amount of data that can be transferred during the replication window with the normal transfer rate, the replication process can't complete and the replication status becomes degraded
.
If this situation occurs, try adjusting the rate of change on the file share and the replication frequency.
Activity tracking events
You can use IBM Cloud® Activity Tracker Event Routing to configure how to route auditing events. Auditing events are critical data for security operations and a key element for meeting compliance requirements. Such events are triggered when you create, modify, or delete a file share. Activity tracker events are also triggered when you establish and use file share replication. For more information, see Activity tracking events for IBM Cloud VPC.
Logging for file share service
After you provision IBM Cloud Logs Routing to add log management capabilities to your IBM Cloud® architecture, you can enable platform logs to view and analyze logs of the File Storage for VPC service. When replication occurs, the file service
generates a regional-file.00002I
log message, which includes information about when the replication occurred, and how much data was transferred. For more information, see Logging for VPC.
Monitoring metrics
You can monitor the read and write throughput, read and write IOPS, number of mount targets, and capacity usage of your share over time in the IBM Cloud console. To see these metrics, go to the file share details page, and click the Monitoring tab.
Monitoring utilization metrics such as total IOPS and total throughput can help you to determine how much work is done by your application or workload. You can use this information to determine whether the IOPS value needs to be adjusted. Monitoring the available capacity of your share can help you identify the need for more storage before insufficient space can become a problem with writing data to the share or replication. Seeing these metrics can help you anticipate any changes in charges at the end of the billing period. These graphs are available to you at no cost, even without an IBM Cloud Monitoring instance.
If you have an instance of the IBM Cloud Monitoring service, click Launch monitoring to launch the Sysdig web UI to work with the metrics dashboards there. In the Sysdig web UI you can view these throughput, IOPS, capacity metrics in more detail, customize your dashboards, and set up alerts. For more information, see Getting started with monitoring and Monitoring metrics for File Storage for VPC.