RE: proactive monitoring
- From: "Ric Van Dyke" <ric.van.dyke@xxxxxxxxxx>
- To: <Joseph.Armstrong-Champ@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 24 Sep 2013 11:46:34 -0500
Instrument the code! Use DBMS_APPLICATION_INFO. Once code is
instrumented with this, tools like OEM and the like CAN track it rather
easily.
Yeap it's "hard" because you have to go in and modify the code some.
- Ric
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Armstrong-Champ,
Joseph William
Sent: Thursday, September 19, 2013 3:55 AM
To: ORACLE-L (oracle-l@xxxxxxxxxxxxx)
Subject: proactive monitoring
How do people do proactive monitoring?
We have certain database level metrics set in OEM that will alert us if
the thresholds get exceeded. The idea is that if we start getting a lot
of these alerts for a particular database, there is a potential problem
which needs attention. I would call this system monitoring.
Now we are being asked to find individual queries which exceed certain
thresholds, but don't necessarily cause the database metric alerts to
go off. It doesn't look like OEM can do this. Does anyone know of
another method?
Thanks.
Joe
--
//www.freelists.org/webpage/oracle-l
--
//www.freelists.org/webpage/oracle-l
Other related posts:
