Re: application monitoring best practices

From: Mark Bobak <Mark.Bobak_at_proquest.com>
Date: Tue, 27 Aug 2013 20:14:39 +0000
Message-ID: <CE4280DA.347D2%Mark.Bobak_at_ProQuest.com>

Damn, never even *heard* of that feature! Never ceases to amaze me how many new Oracle features go unnoticed for who knows how long!

Thanks Kevin!

-Mark
On 8/27/13 3:58 PM, "Kevin Jernigan" <kevin.jernigan_at_oracle.com> wrote:

>Have you looked at Continuous Query Notification - CQN
><http://docs.oracle.com/cd/E11882_01/appdev.112/e41502/adfns_cqn.htm#ADFNS
>018>?
>-KJ
>
>Kevin Jernigan
>+1 650 607.0392 (office) | +1 415 710.8828 (mobile)
>Senior Director, Product Management, Data Layer
>Compression (ACO & HCC) | Resource Management (DBRM & IORM)
>Database Smart Flash Cache | Temporal SQL and CQN
>SecureFiles and filesystems (dNFS & DBFS & CloneDB)
>Database Development, Oracle
>
>On 8/27/2013 12:48 PM, Jeremy Schneider wrote:
>> Have a question for the list. What do you think would be the best way
>>to
>> provide a set of schema-specific alerts with fairly sophisticated
>>trigger
>> and notification settings? OEM (or your general network monitoring
>>tool)
>> or some custom code closer to the application?
>> I have several cases where I need to provide one-off alerts for things
>>like
>> "number of rows in this table exceeds threshold" and the alerts aren't
>>for
>> me personally but for other business groups. Need specific alert
>>messages
>> for "critical" and "clear" thresholds and also the ability to
>>re-generate
>> critical alerts every X hours if the condition continues. Also want to
>> tweak how frequently each check is run (between every 5 to 15 minutes).
>>
>> OEM provides a great framework for handling all sorts of notification
>> situations. I can define the SQL as a Metric Extension. However I'm
>> currently using Administration Groups to automatically apply generic
>> monitoring templates across a broad set of databases... and it seems
>> against this philosophy to start having custom thresholds or
>>notifications
>> on a per-database (not to mention per-schema) level. Nonetheless it
>>seems
>> that any other approach involves a degree of re-inventing the wheel
>>when it
>> comes to the alerts, thresholds, repeated notifications, etc.
>>
>> Thoughts? What's a good architecture for this - am I missing something
>> obvious?
>>
>> -Jeremy
>>
>>
>> --
>> http://about.me/jeremy_schneider
>>
>>
>> --
>> http://www.freelists.org/webpage/oracle-l
>>
>>
>
>
>
>--
>http://www.freelists.org/webpage/oracle-l
>
>
>
>

--
http://www.freelists.org/webpage/oracle-l

Received on Tue Aug 27 2013 - 22:14:39 CEST