Re: OEM 13c question - How to mitigate false positives (noise) without clicking :)
Date: Mon, 27 Jan 2020 16:40:58 +0000
Message-ID: <CABe10sabxCUprs50_XPRxOGajcPz20YzYcGzLrUjQpO16qQ1dg_at_mail.gmail.com>
Hi Koss
You want to look at
On Mon, Jan 27, 2020 at 4:10 PM k.hadd <kouss.hd_at_gmail.com> wrote:
> Hi folks,
https://docs.oracle.com/cd/E24628_01/doc.121/e24473/mon_temp.htm#EMADM12269 and
probably define your own monitoring groups and appropriate templates. We
base our admin groups on the monitoring property Lifecycle Status with more
monitoring for production rather than non-production targets. I'd also
strongly suggest that you create your own templates and strip out the
*thresholds* (not the collection of the metric) for a lot/if not most of
the default metrics. The way I think of metric templates is as "the base
level of monitoring and alerting which all targets should get", you should
end up with a lot of metric data in metric history, but not a lot of
alerting noise.
> A colleague of mine have come across a lot of noise during Oem 13c target
> addition lately even though we have a template. I must say I didn't use OEM
> for centuries so I am pretty noob .
> I understand every target is different but Is there a way to run a
> script/procedure to adjust the common metric thresholds that are known to
> trigger noisy alerts ? I really hate repetitive clicking.
> Even an article about a similar initiative(open source) could help .
>
> Thanks again in advance .
> Koss
>
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Jan 27 2020 - 17:40:58 CET