Get alerted after 5 metric breaches for Response Time (msec) metric

Question

Hi Guys,
Can i edit the Response Time (msec) metric under the Listener Availability Notification rule to alert only if the response time is breaching the alerting threshold for 5 minutes,as in for 5 consecutive occurences when this metric is pooled ?
For example we can execute dbms_server_alert.set_threshold(.....
consecutive_occurrences=>5
for a metric like redo_generated_sec
Can we do this for Response Time (msec) metric under the Listener Availability Notification rule ?
I am also not seeing this metric listed under v$METRICNAME
Any ideas...
Regards,
Swanand

Answer 1

I have no doubt this is it. I switched to the OID of the timeticks that the system has been up for and tried:
<CollectionItem NAME="Response">
<Schedule>
<IntervalSchedule INTERVAL="5" TIME_UNIT="Min"/>
</Schedule>
<Condition COLUMN_NAME="Status" CRITICAL="1" OPERATOR="LT"/>
</CollectionItem>
The corresponding snmpwalk retrieves:
-bash-3.00# ./snmpwalk -Os -v1 -c public 100.100.100.100 .1.3.6.1.2.1.1.3
sysUpTimeInstance = Timeticks: (26302086) 3 days, 1:03:40.86
Now I get a clock once in a while (it looks like its collecting) but then I revert to down. I assume that this structure is basically:
RetrievedValueForStatus OPERATOR CRITICAL triggers a CRITICAL alert and I could add another for WARNING
And then I'm making the assumption that "Running" is the state of CRITICAL or WARNING not being triggered?
I noticed Example 2-9 Default Collection File for Simple Server Alpha uses NO condition.
What happens if the system simply cannot be contacted, is there an assumption that the value is always available in these Conditions? For example, if I return the name of the system in the Snmp Fetchlet and SNMP cannot retrieve ANY values (because the system is down), would the CRITICAL condition be:
<Condition COLUMN_NAME="Status" CRITICAL="" OPERATOR="EQ"/>
I will keep going on trial an error
Thanks...