![](https://secure.gravatar.com/avatar/bbac5d2b97fcfe419a8d8b3842cfe42b.jpg?s=120&d=mm&r=g)
Unless you specifically care about single cores maxing out, you probably only want to alert on “Average” (Which is the usage number task manager / top / etc will show you anyway). A 36 core/thread CPU with 1 core at 100% is only 3% used.
________________________________ Spencer J. Ryan| Manager, Technology and Infrastructure Miller Canfield T +1.313.496.7979 | F +1.313.496.7500 ________________________________
From: Michael via observium observium@lists.observium.org Sent: Wednesday, August 24, 2022 8:53 AM To: observium@lists.observium.org Cc: Michael mich4@gmx.de Subject: [Observium] Help with Alert Checker again / Multiprocessor System
CAUTION EXTERNAL EMAIL: DO NOT open attachments or click links from unknown or unexpected emails.
Hey List,
after fixing the problem with dont check mountpoints, here´s the next one ... we´ve a Server with 2 CPU; I defined an Alert Checker
Entity DeviceHostname Match "*" and Condition "processor_usage gt 95" ...
Now, when I look into my Alert Checkers, I see my Server with Processor "Average" and 2 times "Intel Xeon Processorname ... "
that confuses me a little ... and now the actual Problem:
When Observium send an Alert-Mail, I get 3 Mails ... 1 for "Average" and one for each Processor ... but actually it is enough if I only get one Email ... can I configure this somewhere ?
I helped myself by extend the Entity with "Processor_Description notmatch *average" ... but I don´t know if this is the right way ...
Can somebody help here?
Thanks in advance. Regards, Michael
You have received a message from the law firm Miller Canfield. The information contained in or attached to this electronic mail may be privileged and/or confidential. If you received this transmission and are not the intended recipient, you should not read this message and are hereby notified that any dissemination, distribution or copying of this communication and/or its attachments is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and delete or destroy the original and any copies, electronic, paper or otherwise, that you may have of this communication and any attachments.