application monitoring best practices
Date: Tue, 27 Aug 2013 14:48:23 -0500
Message-ID: <CA+fnDAbRB6h0D+_ZZ4kG2ZcV=Uxckhgiykux3Ymq_RkV8cnEGA_at_mail.gmail.com>
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
Received on Tue Aug 27 2013 - 21:48:23 CEST