Spotting the created topology type name
The newly topology type name is created in the below paths, depends on the database type used:
Oracle UDC topology path:
Configuration | Data | Administration | Management Server | All Data | DBO_Data_Model | Oracle Data Model | Clusters | AGENTNAME| Database | Custom query root | AllQueries | DBO_Cust_"your UDC name" | QueryResults | "yourKeyField" | "your Fieldname" | History/Latest/Current
SQL Server UDC topology path:
Configuration | Data | Administration | Management Server | All Data | DBSS_Data_Model | SQL-Server Data model | Clusters | AGENTNAME |Instances | INSTANCENAME | Custom query root | AllQueries | DBSS_Cust_"your UDC name" | QueryResults | SQL-Server Cust "your UDC name" | "your Fieldname" | History/Latest/Current
DB2 UDC topology path:
Configuration | Data | Administration | Management Server | All Data | DB2_Data_Model | DB2 Data model | Clusters | AGENTNAME |Instances | INSTANCENAME | Custom query root | AllQueries | DB2_Cust_"your UDC name" | QueryResults | DB2 Cust "your UDC name" | "your Fieldname" | History/Latest/Current
Please note that it is a must to navigate to this path as there is a naming convention taking place behind the scenes.
for example, UDC by the name of test will be shown like this (see attached screenshot name.png)
Creating a Rule based upon the UDC topology type name
- Navigate to Administration | Rules & Notifications
- Click on Create Rule
- Enter the Rule Name. Adding the Rule Description and Alarm Description is optional.
- Enter the Rule Type and Rule Triggering choices
- When selecting a "Time Driven" rule triggering, please also select the box "Enable Trigger without Data". This will trigger the alarm where even when no data has changed during the last collection(s)
- Enter the Rule Scope
SQL Server: DBSS_Cust_XXXX
Where XXXX in the name is equal to the name that was used in creating the user defined collection. For example, if the DBSS SQL Server cartridge user defined collection is called version, the rule scope would be named DBSS_Cust_version.
Type in the Topology Type box the new UDC topology type name, and then Validate Rule Scope.
Note: Validate Rule Scope is the far right button under property box (see attached screenshot type_in.png)
- Click the Next button
- Setup the desired condition tabs, IE fatal, critical or warning. Usually the condition for evaluation is comprised of one of the scoped properties against a registry value. In the Run Condition Query, the property should be prefixed and suffixed with # symbols, such as #agent_id#
- After entering the conditions and - if needed - rule actions such as setting up email actions, save the new rule.
The new rule can be administered as any other rule using the Administration | Rules & Notifications | Rule Management dashboard.
The following video provides a walkthrough of how to create a custom rule for a UDC collection.