Re: proactive monitoring

From: Maaz Anjum <maazanjum_at_gmail.com>
Date: Thu, 19 Sep 2013 10:29:12 -0400
Message-ID: <CA+zcOQ8EYd9g16ZN4tY-vV1hh872jAWg4+TprLtxQmbhcqT=Fg_at_mail.gmail.com>



Perfect. Then, as Bobby mentioned, you can use Metric Extension to proactively monitor your application specific metrics. Do you have a metric in mind that you'd like to monitor? For example, processing times for specific types of queries, average batch load times etc.

On Thu, Sep 19, 2013 at 10:26 AM, Armstrong-Champ, Joseph William < Joseph.Armstrong-Champ_at_tufts.edu> wrote:

> OEM 12c (currently 12.1.0.1)****
>
> ** **
>
> *From:* Maaz Anjum [mailto:maazanjum_at_gmail.com]
> *Sent:* Thursday, September 19, 2013 9:58 AM
> *To:* Armstrong-Champ, Joseph William
> *Cc:* ORACLE-L (oracle-l_at_freelists.org)
> *Subject:* Re: proactive monitoring****
>
> ** **
>
> Joe,****
>
> ** **
>
> Which version of OEM are you running?****
>
> ** **
>
> On Thu, Sep 19, 2013 at 9:54 AM, Armstrong-Champ, Joseph William <
> Joseph.Armstrong-Champ_at_tufts.edu> wrote:****
>
> 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
> --
> http://www.freelists.org/webpage/oracle-l
>
> ****
>
>
>
> ****
>
> ** **
>
> --
> A life yet to be lived... ****
>

-- 
A life yet to be lived...


--
http://www.freelists.org/webpage/oracle-l
Received on Thu Sep 19 2013 - 16:29:12 CEST

Original text of this message