Changing rule scope to ignore specific OS or DB user (4333177)

Would be possible to limit one of our rules to not alert on a specific OS or DB user. Specifically, with the SQL Hogs alerts (both cpu and IO), I'm trying to only let it alert if the DB User is not background Oracle stuff (sys, system, dbsnmp, sysman).

This will not be possible through the original rule. The original Ora_CPUHog rule is scoped to the Oracle_Ora_Sql_Hogs_Alert topology object. The definition of this is as follows:

Since the Oracle_Ora_Sql_Hogs_Alert topology does not itself contain the OS_User or User_Name properties, we can't modify the Rule Condition to take into account these properties.
The Ora_Sql_Hogs_Alert collection, however, actually uses the Ora_Sql_Hogs collection. The CPU Metric gathered by the later is used by former as follows:

The value set for CPU Hogs is a measurement of the amount of milliseconds used by a particular session per second. If a statement exceeds this threshold then the CPUHog field in the Ora_SQL_Hogs_Alert table will be marked with a 1, which will then trigger the warning.

The Ora_Sql_Hog collection does contain User_Name and OS_User information. Therefore, the only alternate I can suggest is that a custom rule be created using the Oracle_Ora_Sql_Hog topology object as a scope to restrict which processes are taken into account when the rule evaluates. You would need to create a registry variable for the CPU threshold to measure against, and this would not be dependent on the ASP value set for the agent.