By default, ME metric will not be collected if associated target has a severity on response:state metric. So override this default by explicitly choosing Advanced option while creating ME.
For some databases, ME ( Metric Extension ) is not collecting data. But for the rest databases, it is working fine.
Checking the ME ( Metric Extension ) definition and found an advanced option is not selected.
After creating a new version of this ME ( Metric Extension ) by checking this mentioned option, it works fine.
The reason is this database has frequent Warning/Critical response metric alert. like :
Event Type=Metric Alert Event name=Server_Adaptive_Threshold_Metric:instance_efficiency__response_time_pt Metric Group=Server_Adaptive_Threshold_Metric Metric=Response Time Per Txn Metric value=258.497253691275 Key Value=SYSTEM Rule Name=DEFAULT_RULESET_FOR_ALL_TARGETS,METRIC_ALERT_INCIDENT_CREATION Rule Owner= Update Details: Metrics “Response Time Per Txn” is at 258.497 Incident created by rule (Name = Incident management rule set for all targets, Create incident for critical metric alerts [System generated rule]).
OEM Metric Extension (ME) is a great feature for developing customized metrics, which are unavailable by default.
As we know “Archive Area % Used” metric does not work for using FRA as archive destination when the destination is set to USE_DB_RECOVERY_FILE_DEST. We only receive after “Recovery Area % Used” metric triggers when it hits a Warning threshold of 85% full, and Critical of 97% full.
But the fixed thresholds of 85( Warning )/97( Critical) is not good enough for handling FRA full. So we developed a customized more flexible way to monitor and alert when FRA is used as archive destination.
Subscribe to get access
Read more of this content when you subscribe today.
So, the Metric Extension ( ME) is created successfully, in another post, we will create a Incident Rule which will create an incident and notification for all the over threshold Warning and Critical alerts.