I would like to be able to run a custom alert against the repository without having to choose a database instance.
This is how the custom alert is delivered currently:
SUBJECT
Ignite Alert Notification: Check Status of ENABLE_SQLSTATS (QAFFI2_QARACDB2.FFI.EXPERTCITY.COM) - HIGH
BODY
Alert: Check Status of ENABLE_SQLSTATS
Database Instance: QAFFI2_QARACDB2.FFI.EXPERTCITY.COM
Execution Time: Wednesday - November 26, 2014 09:50:27
View Alert Status: http://omsrac1.qai.expertcity.com:8123/iwc/alertMain.iwc
Alert Parameters:
Description: Check for ENABLE_SQLSTATS
The following instance(s) have incorrect setting for ENABLE_SQLSTATS.
Parameter: ENABLE_SQLSTATS have been disabled on instance EMREP1_OMSRAC1.QAI.EXPERTCITY.COM
Value: 1
As you can see the subject and body contains references to the instance QAFFI2_QARACDB2.FFI.EXPERTCITY.COM, but the actual instance showing the error is EMREP1_OMSRAC1.QAI.EXPERTCITY.COM. This is confusing.
The custom alert if ran against the repository should not require a instance to be chosen. I would like the alert to look something like the following:
SUBJECT
Check Status of ENABLE_SQLSTATS - HIGH
BODY
Execution Time: Wednesday - November 26, 2014 09:50:27
View Alert Status: http://omsrac1.qai.expertcity.com:8123/iwc/alertMain.iwc
Alert Parameters:
Description: Check for ENABLE_SQLSTATS
The following instance(s) have incorrect setting for ENABLE_SQLSTATS.
Parameter: ENABLE_SQLSTATS have been disabled on instance EMREP1_OMSRAC1.QAI.EXPERTCITY.COM
Value: 1
This includes no unnecessary references to other instances and the details can be quickly determined.