| Home | Tips | Papers | Disclaimer | Privacy |
As I no longer work for Quest Software, the following does not in any way represent the views, recommendations or opinions of Quest Software. I do recall however that this information is in the OEBS module help files (I wrote them!)
A feature of the Foglight® Oracle E-Business Suite cartridge is that if a large number of alerts were going to be generated, Foglight® will create a single summary alert and place that alert in a summary table. If however you use this feature YOUR ENTRIES WILL NOT BE SUMMARISED, so you need to be extremely careful when using this custom alerts feature as there are a couple of places in the Foglight® Oracle E-Business Suite cartridge that have the potential to cause an alert storm if there were a large number of exceptions generated from a single check.
The Foglight® OEBS cartridge's Health Check process wakes up every 5 minutes (from memory) and will scan the content of the summary table for any new entries and then display these on the Foglight® console.
All this is described in the Foglight® Cartridge for Oracle E-Business User Guide - something like “Adding your own Health Check”
The Foglight® summary table name is QUEST_FG_OEBS_ALERT_SUMMARY_T and has four columns:
So if you manually add a record to this table the next time the Foglight® Oracle E-Business Suite cartridge health
check wakes up the summary message will be sent to the Foglight® alerts console.
To capture the attention of those of you that bore easily, I have historically presented the power of this feature by showing the following humerous example
INSERT into QUEST_FG_OEBS_ALERT_SUMMARY_T
In a few minutes this alert will show up in the Foglight® console.
Oh the fun…, but remember one person's humour can be another person's insult so it is best to only use this feature for legitimate business purposes.
Please ensure you refrain from using a severity of “Fatal” frivolously as this will generate a Foglight® SLA breach and you will need to
explain that one.
By the way, the summary table is self purging, from memory it holds up to 60 days history. You can therefore
manually delete an entry if appropriate.
On a more serious note - You can also use this feature to create your own Oracle E-Business Suite Foglight
module alerts. All you have to do is write some code that performs your check/s and on exception writes a record
to the summary table. The the Foglight® cartridge was deliberately designed this way so you can add your own custom alerts.
Note: This feature is only available for the Foglight® Oracle E-Business Suite cartridge as the summary table does
not exist in other modules.
Timestamp The time the alert was generated - usually sysdate
Alertid Alert ID to appear in the Foglight® alerts console
Severity Warning, Critical, and Fatal (spelling and case sensitive).
Details The alert message that will appear in the Foglight® alerts console
VALUES ( sysdate, ‘OEBS001’, ‘Critical’, ‘Foglight has detected there is insufficient beer in the fridge’);
The example package piper_rx_fog_custom_alerts.pkb contains four simple examples. These are deliberately simple and may contain PLSQL errors so be warned!
To run the check every 15 minutes, you could use a database job
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
(
job => X
,what => 'PIPER_RX_FOG_CUSTOM_ALERTS.CHECK_ACTIVE_USERS (50);'
,next_date => to_date('01-29-2009 07:00:00','mm/dd/yyyy hh24:mi:ss')
,interval => 'SYSDATE+15/1440 '
,no_parse => TRUE
);
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || TO_CHAR(x));
END;
/
This example will continue to alert every check interval whilst the number of users remains above the alert level.
To run the check every 15 minutes, you could use a database job
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
(
job => X
,what => 'PIPER_RX_FOG_CUSTOM_ALERTS.CHECK_COMPLETED_ERROR (10);'
,next_date => to_date('01-29-2009 07:00:00','mm/dd/yyyy hh24:mi:ss')
,interval => 'SYSDATE+15/1440 '
,no_parse => TRUE
);
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || TO_CHAR(x));
END;
/
In this example, alerts are keyed on the Foglight® alertid by adding the concurrent request ID to the alert_id. The Foglight alertid will be unique for each FSG and will only report on new FSGs submitted. In this example we also only report on requests submitted after the last time an entry was added to the Foglight® summmary table
To run the check daily at 7:00am, you could use a database job
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
(
job => X
,what => 'PIPER_RX_FOG_CUSTOM_ALERTS.CHECK_FOR_MY_BIRTHDAY;'
,next_date => to_date('01-29-2009 07:00:00','mm/dd/yyyy hh24:mi:ss')
,interval => 'TRUNC(SYSDATE+1)+7/24'
,no_parse => TRUE
);
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || TO_CHAR(x));
END;
/
You can configure the standard Foglight® application so that selected alert IDs (your custom alerts) send notifications (e-mail, SMS etc) to selected individuals. i.e. All alerts with alerted = ‘SPECIAL-001’ are to notify user X
This principle can be used to check and alert on any application or functional activity limited only by your imagination.Eg
Let your imagination run riot.
WARNING - BEFORE YOU DO ANYTHING
Please refer to our Disclaimer.
Oracle®, Oracle Applications® & Oracle E-Business Suite® are registered trademarks of Oracle Corporation
TOAD® & Foglight® are registered trademarks of Quest Software
© 2009 G Piper
All Rights Reserved.