---
name: vpc-file_storage_vpc_monitoring
title: Monitoring file share health states, lifecycle status, and events
description: Monitor File Storage for VPC health states, lifecycle status, and events by using the console, CLI, or API to track share operations.
last-updated: 2026-06-26
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/vpc?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Monitoring file share health states, lifecycle status, and events
{: #fs-vpc-monitoring}

Monitor File Storage for VPC health states, lifecycle status, and events by using the console, CLI, or API to track share operations.
{: shortdesc}

## File share statuses
{: #file-share-statuses}

When you [view the list of your file shares in the console](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=ui&format=markdown), you can see the status of each file share in the second column.
{: ui}

When you [view file share details from the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=cli&format=markdown) by running either `ibmcloud is shares` or the `ibmcloud is share` command, the response contains the `Status` of the displayed file share.
{: cli}

When you make a [`GET /shares` request](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=api&format=markdown), the API returns a `lifecycle_state` value as part of the information about the file share.
{: api}

Table 1 shows the lifecycle statuses that the file share can have.

| Status      | Explanation |
|-------------|-------------|
| `stable`    | The file share or mount target is stable and available for use. |
| `pending`   | The file share or mount target is being created. |
| `failed`    | The file share or mount target failed to be created. You can delete the failed share and try creating another one. \n This status is also shown when the access to the origin share is revoked from the accessor share.|
| `deleting`  | The file share or mount target is being deleted. |
| `suspended` | The file share violates [IBM Cloud® Terms of Use](https://cloud.ibm.com/docs/overview?topic=overview-terms&format=markdown). A suspended file share cannot be updated or deleted.|
| `updating`  | The file share capacity or IOPS is being updated.|
| `waiting`   |  |
{: caption="File Storage lifecycle states" caption-side="bottom"}

## File share replication status
{: #file-share-replication-status}

When you [view your file share in the console](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=ui&format=markdown), you can see its Replication role and Replication status. This information is displayed in the file shares list and the file share details page in the File share replication relationship section.
{: ui}

When you [view the details of a file share from the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=cli&format=markdown#fs-share-details-cli) by running the `ibmcloud is share` command, the response contains the `Replication status` of the specified file share.
{: cli}

When you make a [`GET /shares/{id}` request](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=api&format=markdown#fs-single-file-shares-api), the API returns a `replication_status` value as part of the information about the file share.
{: api}

Table 2 shows all the replication status that the file shares can have.

| Status            | Explanation |
|-------------------|-------------|
| `active`          | This share is actively participating in replication, and the replica's data is up to date with the replication schedule. |
| `failover_pending`|  This share is performing a replication failover. Or the service is waiting for another operation to complete, such as file share expansion, before the failover can commence. |
| `initializing`    | This share is initializing replication. |
| `none`            | This share is not participating in replication. |
| `split_pending`   | This share is performing a replication split. |
{: caption="File Storage replication status" caption-side="bottom"}

## Replication sync health
{: #fs-repl-synchealth}

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 console](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=ui&format=markdown#fs-view-single-share-ui).
{: 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](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=cli&format=markdown#fs-share-details-cli).
{: cli}

You can programmatically retrieve the last sync details by calling the `/shares` method in the [VPC API](https://cloud.ibm.com/docs/apis/vpc/latest#get-share){: external}. 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](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-view&interface=api&format=markdown#fs-single-file-shares-api).
{: 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
{: #fs-activity-tracker}

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 tracking events are also triggered when you establish and use file share replication. For more information, see [Activity tracking events for IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-at_events&format=markdown).

## Logging for file share service
{: #fs-event-la-logs}

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](https://cloud.ibm.com/docs/vpc?topic=vpc-logging&format=markdown#logging-file-share-replication).

## Monitoring metrics
{: #fs-sysdig-mon}

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 open the Sysdig web UI to work with the metrics dashboards there. In the Sysdig web UI you can view the throughput, IOPS, and capacity metrics in more detail, customize your dashboards, and set up alerts. For more information, see [Getting started with monitoring](https://cloud.ibm.com/docs/monitoring?topic=monitoring-getting-started&format=markdown) and [Monitoring metrics for File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-fs-vpc-monitoring-sysdig&format=markdown).