Cloud Storage Gateway:Query and handle event alerts

Query alerts on all gateways in a region

1. Log on to the CSG console.

2. In the left-side navigation pane, click Event Alerts. On the Event Alerts page, you can view the alert information described in the following table.

   Parameter	Description
   Alert Type	The following alert types are supported for file gateways: Insufficient space for metadata cache Throttled Piled upload queue
   Alert Level	The alert level.
   Gateway ID	The ID of the gateway on which the alert is triggered. Note You can click the gateway ID to view the alerts of the gateway.
   Share Name	The share on which the alert is triggered.
   Solution	The event handling solutions. You can click links to view how to handle alerts.
   Alert Time	The time when the alert was first reported.
   Closed At	The time when the alert was closed. If the alert is not closed, Not closed is displayed.

You can search for alerts by time, gateway ID, share name, and alert status.

Query alerts on a gateway

1. Log on to the CSG console.

2. In the left-side navigation pane, click Gateways. On the page that appears, locate the file gateway and click the ID of the file gateway.

3. Click the Event Alerts tab to view alerts. The following table describes the alert information.

   Parameter	Description
   Alert Type	The following alert types are supported for file gateways: Insufficient space for metadata cache Throttled Piled upload queue
   Alert Level	The alert level.
   Gateway ID	The ID of the gateway on which the alert is triggered.
   Share Name	The share on which the alert is triggered.
   Solution	The event handling solutions. You can click links to view how to handle alerts.
   Alert Time	The time when the alert was first reported.
   Closed At	The time when the alert was closed. If the alert is not closed, Not closed is displayed.

You can search for alerts by time, share name, and alert status.

Insufficient space for metadata cache

Cause

The space for metadata cache is the space reserved in cache disks of Server Message Block (SMB) or Network File System (NFS) shares to store metadata, most of which is directory structure information. The larger the number of files in a share is, the more space the metadata cache requires. A cache disk contains space reserved for data cache and metadata cache. By default, 20% of the cache disk space is reserved for metadata cache. This alert is triggered if the remaining metadata cache space is less than 3 GB or 20% of the total metadata cache size.

Handling method

We recommend that you increase the cache disk space to prevent write failures caused by insufficient metadata cache space. For more information, see Increase cache disk capacity.

Throttled

Cause

This alert is triggered if the amount of data that is simultaneously written to the cache disk is greater than 80% of the total data cache size. In this case, data writes may fail.

Handling method

1. Troubleshoot problematic data uploads that cause failures in releasing cache space. The following factors cause problematic uploads:

• You attempt to upload data to a bucket that does not exist.

• The bucket policy denies access from the gateway.

• The storage class of the bucket is Archive or Cold Archive.

• The size of files that are being simultaneously written to the cache disk exceeds the size of available data cache. As a result, the files cannot be closed and uploaded within the expected period of time.

2. Decrease the amount of data that can be simultaneously written to the cache disk.

3. Increase the cache capacity of the share. For more information, see Increase cache disk capacity.

Piled upload queue

Cause

This alert may be triggered by the following factors:

• You attempt to upload data to a bucket that does not exist.

• The bucket policy denies access from the gateway.

• The gateway is mapped to an Archive bucket or a Cold Archive bucket.

Handling method

Use the following steps to troubleshoot the alert:

1. Check whether the bucket exists. If the bucket does not exist, use an existing bucket.

2. Check whether access policies configured for the bucket deny access from the gateway.

3. Check whether the storage class of the bucket is Archive or Cold Archive. We recommend that you use a Standard bucket together with a gateway if your business application does not necessarily require a bucket in another storage class.

If the preceding steps cannot resolve the alert, contact us.