Custom Group and Alert creation in Aria Operations
book
Article ID: 301452
calendar_today
Updated On:
Products
VMware Aria Suite
Issue/Introduction
This article is to outline the process of cloning and modifying an alert and Policy for the purpose of turning it off or setting different thresholds for a specific Custom Group of Objects.
Clone Guest File system space usage Symptoms with adjusted values
Clone Guest file system alert with adjusted symptoms
Add Policy to default policy with original guest file alert turned off and new Cloned alert "Activated"
create Custom group linked to new policy with vRLI nodes included.
Clone Symptom and adjust the values.
Go to “Configure -> Alerts -> Symptom Definitions”
Here we can filter for the Symptom we are looking for: “Guest File System space usage at warning level”
Click the 3 dots next to the Symptom we want and click “Clone”
Now you will want to change the name of the Symptom and the value. For our example we’re changing the name to “vRLI - Guest File System space usage at warning level”
We’re also changing the condition value from 90 to “98”
Click Save
For our example we will repeat steps a–f with the “Guest File System space usage at critical level” Symptom, setting the value to “99”.
Clone the Alert and replace Symptoms with newly created ones.
Go to “Configure -> Alerts -> Alert Definitions”
Here we can filter for the Alert we are looking for: “One or more virtual machine guest file systems are running out of disk space”
Click the 3 dots next to the Alert we want and click “Clone”
Now you will want to change the name of the Symptom. For our example we’re changing the name to “vRLI - One or more virtual machine guest file systems are running out of disk space” and click Next
On the right side you can search for the desired symptom. In our case we are looking for the symptoms we just cloned and renames so we’re filtering for the term “vRLI”. Then we can see the 2 new symptoms we cloned in Section 1. - Make sure to click on “Symptoms”
Now we can drag over both symptoms from the right over to the left side.
Delete the original Symptoms from the left side by clicking the “X” next to them. When you’re done, it should look like the screenshot below.
Click Update or Create
Add Policy to default policy with original guest file alert turned off and new Cloned alert "Activated"
Go to “Configure -> Policies -> Policy Definitions”
Select your active Policy, then click on Add
Give your New Policy a name. (This will only be to affect the vRLI Custom Group we will create later.) For our Example, we’re calling it “Aria Operations for Logs”
Make sure you select the “Inherit From:” to your active default policy.
Click Create Policy
Click on Alerts and Symptoms
Here we need to look for the Alert definitions we need to activate and deactivate. Type into the filter a search parameter for the previously affected alerts. For our example we will type in: “Guest File System”
Now you should see the “Old Default Alert”, click on the drop down box under the “State” Column, and set it to Deactivated
You can then look for the new Alert. (For our example it shows up under the same filter) And set that Alert to Activated.
Hit Save
Create a custom group for the affect Objects
Go to “Environment - > Custom Groups”
Click on Add
Give the group a name
Select the Type of Group, for our example we are setting to “Manual Application”
Set Policy to the new Policy we created in Section 3 and click Next
We can now set the criteria for our custom group. For our example we will just go to the “Objects to Always include” section and manually specify the names of the Log Insight nodes. Then click Add to include them in the Objects to Always include
Click OK
That’s it. From Now on the VMs specified in the group will not be affected by the original “Guest File System usage” Alerts and instead will use the new alerts with the higher thresholds.