Step-By-Step Create OEM Metric Extension - Send Alerts on Long Running SQLs Using Metric Extension

In this tutorial, I am demonstrating the steps to create Metric Extension in OEM along with constructing the SQL queries to be used and how we can use a Metric Extension to send alerts on long running or under-performing SQLs.
A metric extension is an extension to OEM's default capacity to collect certain metric on its targets. For example, OEM collects metrics like tablespace usage, file system usage, number of error logged in alert.log etc. But it does not automatically collect data on SQLs and alert on long running SQLs. To achieve this we will extend OEM's capacity to collect metric data on SQLs running in the database targets and based on conditions applied, the Metric Extension will send critical, warning or clear alerts.
Please note that the run frequency of the ME should be ideally set to a number between half of the threshold minutes and the full threshold minutes set for detecting long running SQLs. For example, if you are trying to catch SQLs running longer than 10 minutes, then the run frequency of the ME should be a number between 5 and 10 (max). If you set smaller frequency like 5, you are less likely to miss an alert. So it is suggested to set a smaller number as run frequency for the ME.
Please watch the video and leave me comments if you have any.
For the SQL queries used, please download the text file from my google drive:
drive.google.c...