You are receiving the following alert for your vCenter Server Appliance's /storage/archive partition:
One or more guest file systems of the virtual machine are running out of disk space. Check the symptom details to identify the affected guest file system
Environment
VMware Aria Operations 8.x
Resolution
To exclude the /storage/archive file system from triggering the alert, perform the following steps.
1. Create Custom Symptom Definitions for Critical and Warning Level that Excludes /storage/archive
Log in to Aria Operations with an administrative level user account
Navigate to Operations > Configurations > Symptom Definitions.
Click the Click here to apply filters button (funnel icon)
Type Guest file system space in the Name: field
Type Virtual Machine in the Object Type: field
Click Apply
Click the vertical three dots button next to the Guest file system space usage at critical level symptom and select Clone.
Change the name of the cloned copy of the symptom as desired to identify it as a custom critical level symptom
Expand AdvancedSettings and check the box Evaluate on instance Metrics.
Expand Guest File System on the right and then expand /storage/archive.
Note: If /storage/archive cannot be found, click the Select Specific Object button and filter for a vCenter Server Appliance VM then click Select
Under the /storage/archive/ filesystem, drag the Partition Utilization (%) metric over so it appears under the list of excluded metric instances.
Click Save.
Highlight the symptom definition you just created and click the vertical 3 dots button and select Clone.
Change the name of the cloned copy of the symptom as desired to identify it as a custom warning level symptom
Change the Critical drop down to Warning.
Change the Numeric value to 90.
Click Save.
2. Create a Custom Alert that Uses the Custom Symptom Definitions
Navigate to Operations > Configurations > Alert Definitions
Click the Click here to apply filters button (funnel icon)
Type guest file systems in the Name: field
Type Virtual Machine in the Object Type: field
Click Apply
Click the vertical three dots button next to the One or more virtual machine guest file systems are running out of disk space alert definition and select Clone.
Change the name of the cloned copy of the alert as desired to identify it as a custom alert definition
Click the Remove Symptom button (X icon) next to the two original symptoms for Guest file system space usage at critical level & Guest file system space usage at warning level.
Click the Symptoms tab in the right panel and filter for the symptoms created in steps 1.d and 1.e.
Drag the new symptoms to the left box that says Drag and drop metric to specify its condition or symptom into your alert here to create a new set.
Click Create
3. Create a New Policy to Disable the OOTB Alert and Symptoms and Enable the Custom Alert and Symptoms
Navigate to Configure> Policies > Policy Definition.
Note the name of the policy with a D in the priority column
Click Add
Name the policy as desired to indicate it is a custom policy
Select the policy noted in step 3.b in the Inherit From: field.
Click Create Policy
Click Alerts and Symptoms
Click the Alert Definitions tab if it is not automatically selected
Type Virtual Machine in the Select Object Type field and select Virtual Machine from under vCenter
Type guest file systems in the Type here to apply filters box and press Enter
Click the State drop down for the One or more virtual machine guest file systems are running out of disk space alert and select Deactivated.
Filter for the alert definition created in step 2.c
Click the State drop down and select Activated (Enabled on older versions) for the custom Alert
Click the Symptom Definitions tab
Type Virtual Machine in the Select Object Type field and select Virtual Machine from under vCenter
Type guest file system space in the Type here to apply filters box and press Enter
Click the State drop down for the Guest file system space usage at critical level & Guest file system space usage at warning level symptoms and select Deactivated.
Filter for the symptom definitions created in steps 1.d and 1.e
Click the State drop down and select Activated (enabled on older versions) for both custom symptoms
Click Save
Click Close (X icon in top right corner)
4. Create a Custom Group for the vCenter Objects and Apply the Custom Policy
Navigate to Operations > Configurations and click Custom Groups
Click Add to create a new Custom Group
Name the custom group as desired
Select Environment in the Group Type field
Select the custom policy created in step 3.c in the Policy field
Under Define Membership Criteria, select Object Name, then Contains, and enter your vCenter Server Appliance name(s).
Click the Preview button to ensure the group membership has populated
Click Create
5. Validate the Change
Search for your vCenter Server Appliance in the Aria Operations inventory and navigate to the Summary page
Hover your cursor over the POLICY icon in the top right corner
Validate that the policy created in step 3 is the policy shown
If the wrong policy is shown, navigate to Configure > Policies > Policy Definition
Click the vertical three dots button and select Reorder Policies
Configure the Policy order as desired (see Policies)