RE: "Excluded Objects" syntax in OEM

Thx for the info Rich. I believe you pulled that info from either checking metric settings for a specific target or on a Monitoring Template. Just to be clear, I'm fine with the metrics getting captured and Incidents being flagged. What I don't want is to get alerted on specific errors, which is in the realm of Incident Rules. For the metric "Generic Incident", as for I think all metrics in Incident Rules, you get all "Objects" by default, if it applies, or else you filter on objects you want or don't want. My question is around what "Objects" means in this context. I was assuming it'd be a perl-like reg expression but I'm not positive. Each field as a plus sign to click for what implies a selection list of objects to choose from. But the pop-up doesn't give any hints as to what to enter. That has 2 fields, one labeled "Key" and the other no label. If I use the pre-filled "%" in each one and click "Go" it tells me I need to enter something beyond that, which doesn't help.

Make sense?

Regards,

Dave

From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of Rich J Sent: Thursday, February 27, 2020 2:06 PM To: oracle-l_at_freelists.org
Subject: Re: "Excluded Objects" syntax in OEM

CAUTION: This email originated from outside of D&B. Please do not click links or open attachments unless you recognize the sender and know the content is safe.

Hey Dave,

One database target in my EM13.3 has the Generic Alert Log Error metric. In the Edit Advanced Settings for that metric, there is an "Alert Log Filter Express" at the bottom. This filter has the description of:

This expression must be a Perl-style regular expression and only an exact match of the pattern will suppress. If there is an ORA- error occurring in the alert log that should not be considered a Generic Alert Log Error, it can be filtered out by supplying a Filter Expression. When the ORA- error stack fully matches this expression, Oracle Enterprise Manager will ignore the ORA- error entirely. Example: To match "ORA-00600: internal error code, arguments [qerfxFetch_01], [], [], [], [], [], []" you might give the pattern ".*ORA-00600:.*\[qerfxFetch[^\]]*\].*".

The current Property Value of this for me is:

.*ORA-0*(54|1142|1146)\D.* So, errors matching that pattern (the globby ".*" at the start and end are interesting) should be excluded from the warning and critical thresholds. Does that help you at all?

Rich

On Thu, Feb 27, 2020 at 11:52 AM Herring, David <dmarc-noreply_at_freelists.org<mailto:dmarc-noreply_at_freelists.org>> wrote: Folks,

I'm trying to figure out what the proper syntax is for having particular ORA- errors to be excluded from Incident Rules and not having much luck. I could have sworn that in the past regular expressions worked but now I'm doubting it. This is for OEM 13.3, RHEL 6.9.

(Note: I've got an SR open w/ Oracle on this as well but thought I'd check with this list as you tend to have more real-world examples to work off of)

[snip]

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