As I proceed forward, can you tell me- is this coming from this one host
or more than one host with database?
So let's start with the important aspects of the notification, bypassing
what we don't need to worry about, (or shouldn't have to...)
The rule set we need to work with is *MTC_MECC_DMAS*
1. In this rule, we need to determine, do you currently have this rule set
configured for *Warnings* and *Critical*? You may need to duplicate the
rule to a second one and separate the two, so you still receive critical
and can silence warning notifications for this metric.
2. You can then choose to edit the rule set, go to the rule: *MTC_MECC_DMAS
Incident All Targets,Create incident for critical metric alerts*
3. Catagory: Load
4. Next, the Metric Group: Server_Adaptive_Threshold_Metric- Notice that
this says "Adaptive". Keep that in mind for a metric that doesn't have a
distinct threshold value but one that adapts to the system load.
I would consider the following:
If, IF, it's only this host or a group of hosts that are impacted by this
warning alert that you don't want to have notifications for, consider
isolating this group/host from the rule for warnings and not have it alert
on this one metric.
-This is easily done by right clicking on the existing rule and duplicating
it inside the rule set and then update the original to alert on critical
and the second one to only alert on warnings.
In the rule for warnings, either remove this metric alert, edit the metric
to exclude this host.
Using the blog post I originally sent you, you can silence this alert while
having consistent and important information continue to be alerted on, but
you'll need to break down your rules, which can be seen in this post, here:
http://dbakevlar.com/2013/09/em12c-enterprise-monitoring-part-v-warning-management/
Thank you, let me know if you need more assistance.
Kellyn Pot'vin-Gorman
[image: --]
Kellyn Pot'Vin-Gorman
[image: https://]about.me/dbakevlar
<https://about.me/dbakevlar?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=chrome_ext>
[image: Kellyn Pot'Vin on about.me]
Kellyn Pot'Vin-Gorman
about.me/dbakevlar
<http://about.me/dbakevlar>
On Tue, Dec 26, 2017 at 6:17 AM, Ashoke Mandal <ramukam1983@xxxxxxxxx>
wrote:
Hi Kellyn, Here is the details of the alert. This alert is is coming too
many times and flooding my Inbox. Any help will be appreciated. Thanks,
Ashoke
Host=*<Host_Name>*
Target type=*Database Instance*
Target name=*<DB_Name>*
Categories=*Load*
Message=*Metrics "Logons Per Sec" is at 149.676*
<https://gva04cn1.lau.medtronic.com:7800/em/redirect?pageType=sdk-core-event-console-detailEvent&issueID=600D37F6B8350327E054001B2194CD2D>
Severity=*Warning*
Event reported time=*Dec 26, 2017 6:02:38 AM MST*
Operating System=*SunOS*
Platform=*sparc*
Associated Incident Id=*2606*
<https://gva04cn1.lau.medtronic.com:7800/em/redirect?pageType=sdk-core-event-console-detailIncident&issueID=613EE5C7DFBA26EDE054001B2194CD2D>
Associated Incident Status=*New*
Associated Incident Owner=
Associated Incident Acknowledged By Owner=*No*
Associated Incident Priority=*None*
Associated Incident Escalation Level=*0*
Event Type=*Metric Alert*
Event name=
*Server_Adaptive_Threshold_Metric:instance_throughput__logons_ps*
Metric Group=*Server_Adaptive_Threshold_Metric*
Metric=*Cumulative Logons Per Sec
<https://gva04cn1.lau.medtronic.com:7800/em/redirect?pageType=sdk-core-metric-details&timePeriod=byDay&metric=Server_Adaptive_Threshold_Metric&target=thdmas.dmas.medtronic.com&metricColumn=instance_throughput__logons_ps&type=oracle_database&keyValue=SYSTEM>*
Metric value=*149.675702644271*
Key Value=*SYSTEM*
Rule Name=*MTC_MECC_DMAS Incident All Targets,Create incident for
critical metric alerts*
Rule Owner=*SYSMAN*
Update Details:
Metrics "Logons Per Sec" is at 149.676
Incident created by rule (Name = MTC_MECC_DMAS Incident All Targets,
Create incident for critical metric alerts; Owner = SYSMAN).
On Mon, Dec 25, 2017 at 8:42 PM, Kellyn Pot'Vin-Gorman <
dbakevlar@xxxxxxxxx> wrote:
Can you please paste the alert you receive, editing out andy company Info
here? The alert contains the data to isolate the metric.
Thank you,
Kellyn
On Sun, Dec 24, 2017 at 2:16 PM Ashoke Mandal <ramukam1983@xxxxxxxxx>
wrote:
I have disabled the entire Throughput Metric (containing *Cumulative *Logons
Per Sec) but it doesn't help and still receiving too many alerts on Metrics
"Logons Per Sec".
I am still looking for help on how to turn off this alert.
Thanks,
Ashoke
On Fri, Dec 22, 2017 at 3:55 PM, Ashoke Mandal <ramukam1983@xxxxxxxxx>
wrote:
Hello Kellyn and Mladen, Thanks for your reply.--
*So far I found out Throughput Metric and **that** has Cumulative *Logons
Per Sec. I have disabled the entire Throughput Metric and will see if that
stops this warning alert.
*under *Oracle Database -> Monitoring -> All Metrics -> Throughput
Ashoke
On Fri, Dec 22, 2017 at 1:14 PM, Mladen Gogala <gogala.mladen@xxxxxxxxx
wrote:
The most probable cause is having both OEM with Grid Control DB and a
local EM running.
Regards
On Fri, 22 Dec 2017 09:43:32 -0600
Ashoke Mandal <ramukam1983@xxxxxxxxx> wrote:
Dear All,(12.1.0.5).
I have migrated some of our databases from OEM 11g to OEM 12c
It working OK but getting too many extra warning like this.Sec" is
EM Event: Warning:thdmas.dmas.medtronic.com - Metrics "Logons Per
at 105.409metric in
I would like to disable this but not able to locate the related
12c OEM console.following area
I logged into the database via OEM 12C and checked under the
but not able to find the Metrics "Logons Per Sec" .
Oracle Database -> Monitoring -> Metric and collection settings
Oracle Database -> Monitoring -> All Metrics
Any help will be highly appreciated.
Thanks,
Ashoke
--
Mladen Gogala
Oracle DBA
Tel: (347) 321-1217
[image: Kellyn Pot'Vin on about.me]
Kellyn Pot'Vin-Gorman
about.me/dbakevlar
<http://about.me/dbakevlar>
