|
|
| Subject: | /Perf/CPU Events no longer clearing |
| Author: | Martin |
| Posted: | 2016-05-27 03:02 |
Good Morning,
some weeks go i migrated all my data from Zenoss 4.2.5 to Zenoss 5. I'm running the latest version. Unfortunately my /Perf/CPU events are no longer clearing if CPU load decreases again. This workes for me in version 4.2.5 for a long time. Any hints are appreciated!
CPU load is gathered by SNMP and has MinMaxTreshold set with event class /Perf/CPU. Event class has the following transform:
import re
if evt.summary.startswith('threshold of CPU Load exceeded'):
lincpu = re.search("current value ([\d\.]+)", evt.summary)
if lincpu:
currentcpu = float(lincpu.group(1))
evt.component = "CPU"
evt.summary = "High CPU Utilization: Currently %3.0f%%" % (currentcpu)
evt.message = evt.summary
Thank you, Martin
| Subject: | Any ideas please? Thank you. |
| Author: | Martin |
| Posted: | 2016-06-01 01:30 |
Any ideas please
Thank you.
| Subject: | Are the events still being |
| Author: | Jay Stanley |
| Posted: | 2016-06-01 09:56 |
Are the events still being edited by the transform Also, can you see a clear event happening (adjust your filters)
| Subject: | Yes, events are edited by an |
| Author: | Martin |
| Posted: | 2016-06-02 00:56 |
Yes, events are edited by an transform that converts CPU load to percentage. Filters are checked properly. Since i moved to Zenoss 5.* i don't see clear events. That's exactly the issue but unfortunately i cannot figure out the cause.
| Subject: | Can you run zenperfsnmp -v10 |
| Author: | Jay Stanley |
| Posted: | 2016-06-02 06:38 |
Can you run zenperfsnmp -v10 against the device and capture the output We will be able to see the clear event there if there is one.
Also, could I get a screen capture of your threshold
| Subject: | Currently we have a CPU load |
| Author: | Martin |
| Posted: | 2016-06-02 07:25 |
Currently we have a CPU load alarm for device abc.
--------------
[zenoss@9d44f4c75ef2 ~]$ zenperfsnmp run -v10 --device=abc
2016-06-02 12:20:22,294 DEBUG zen.zenperfsnmp: _checkZenHub: entry
2016-06-02 12:20:22,294 DEBUG zen.zenperfsnmp: ZenHub health check: ZenHub may be down.
2016-06-02 12:20:22,294 DEBUG zen.zenperfsnmp: _signalZenHubAnswering(False)
2016-06-02 12:20:22,294 DEBUG zen.zenperfsnmp: removing file at /opt/zenoss/var/zenhub_connected
2016-06-02 12:20:22,295 DEBUG zen.zenperfsnmp: Starting PBDaemon initialization
2016-06-02 12:20:22,296 INFO zen.zenperfsnmp: Connecting to localhost:8789
2016-06-02 12:20:22,296 DEBUG zen.pbclientfactory: Starting connection...
2016-06-02 12:20:22,296 DEBUG zen.zenperfsnmp: Logging in as admin
2016-06-02 12:20:22,300 DEBUG zen.pbclientfactory: Connected
2016-06-02 12:20:22,300 DEBUG zen.pbclientfactory: Cancelling connect timeout
2016-06-02 12:20:22,301 DEBUG zen.pbclientfactory: Sending credentials
2016-06-02 12:20:22,303 DEBUG zen.pbclientfactory: Cancelling connect timeout
2016-06-02 12:20:22,304 INFO zen.zenperfsnmp: Connected to ZenHub
2016-06-02 12:20:22,304 DEBUG zen.zenperfsnmp: Setting up initial services: EventService, Products.ZenHub.services.SnmpPerformanceConfig
2016-06-02 12:20:22,305 DEBUG zen.zenperfsnmp: Chaining getInitialServices with d2
2016-06-02 12:20:22,305 DEBUG zen.pbclientfactory: pinging perspective
2016-06-02 12:20:22,312 DEBUG zen.zenperfsnmp: Loaded service EventService from zenhub
2016-06-02 12:20:22,312 DEBUG zen.zenperfsnmp: Loaded service Products.ZenHub.services.SnmpPerformanceConfig from zenhub
2016-06-02 12:20:22,312 DEBUG zen.zenperfsnmp: Queued event (total of 1) {'rcvtime': 1464870022.312403, 'severity': 0, 'component': 'zenperfsnmp', 'agent': 'zenperfsnmp', 'summary': 'started', 'manager': '9d44f4c75ef2', 'device': 'localhost', 'eventClass': '/App/Start', 'monitor': 'localhost'}
2016-06-02 12:20:22,312 DEBUG zen.zenperfsnmp: Sending 1 events, 0 perf events, 0 heartbeats
2016-06-02 12:20:22,313 DEBUG zen.zenperfsnmp: Calling connected.
2016-06-02 12:20:22,313 DEBUG zen.collector.config: Heartbeat timeout set to 900s
2016-06-02 12:20:22,313 DEBUG zen.collector.scheduler: add task configLoader,
2016-06-02 12:20:22,313 DEBUG zen.zenperfsnmp: Performing periodic maintenance
2016-06-02 12:20:22,314 DEBUG zen.pbclientfactory: perspective ponged
2016-06-02 12:20:22,314 DEBUG zen.pbclientfactory: Cancelling ping timeout
2016-06-02 12:20:22,314 DEBUG zen.collector.scheduler: Task configLoader starting (waited 0 seconds) on 1200 second intervals
2016-06-02 12:20:22,314 DEBUG zen.collector.scheduler: Task configLoader changing state from IDLE to QUEUED
2016-06-02 12:20:22,314 DEBUG zen.collector.scheduler: Task configLoader changing state from QUEUED to RUNNING
2016-06-02 12:20:22,314 DEBUG zen.collector.config: configLoader gathering configuration
2016-06-02 12:20:22,315 DEBUG zen.collector.config: Fetching daemon configuration properties
2016-06-02 12:20:22,350 DEBUG zen.MetricWriter: publishing metric eventQueueLength 0 1464870022.35 {'daemon': 'zenperfsnmp', 'monitor': 'localhost', 'metricType': 'GAUGE', 'tenantId': 'cykew3tdcdk9oxtqesrzheygp', 'instance': '0', 'internal': True}
2016-06-02 12:20:22,350 DEBUG zen.publisher: writing: {"timestamp":1464870022.35023,"metric":"eventQueueLength","value":0.0,"tags":{"daemon":"zenperfsnmp","monitor":"localhost","metricType":"GAUGE","tenantId":"cykew3tdcdk9oxtqesrzheygp","instance":"0","internal":true}}
2016-06-02 12:20:22,350 DEBUG zen.MetricWriter: publishing metric eventQueueLength 0 1464870022.35 {'daemon': 'zenperfsnmp', 'monitor': 'localhost', 'metricType': 'GAUGE', 'tenantId': 'cykew3tdcdk9oxtqesrzheygp', 'instance': '0', 'internal': True}
2016-06-02 12:20:22,350 DEBUG zen.publisher: writing: {'timestamp': 1464870022.350232, 'metric': 'eventQueueLength', 'value': 0.0, 'tags': {'daemon': 'zenperfsnmp', 'monitor': 'localhost', 'metricType': 'GAUGE', 'tenantId': 'cykew3tdcdk9oxtqesrzheygp', 'instance': '0', 'internal': True}}
2016-06-02 12:20:22,371 DEBUG zen.collector.scheduler: Task configLoader changing state from RUNNING to FETCHING_MISC_CONFIG
2016-06-02 12:20:22,371 DEBUG zen.zenperfsnmp: Updated configCycleInterval preference to 360
2016-06-02 12:20:22,371 DEBUG zen.zenperfsnmp: Changing config task interval from 20 to 360 minutes
2016-06-02 12:20:22,371 DEBUG zen.collector.scheduler: Stopping task configLoader,
2016-06-02 12:20:22,371 DEBUG zen.collector.scheduler: call finished LoopingCall<1200>(CallableTask: configLoader, *(), **{}) : LoopingCall<1200>(CallableTask: configLoader, *(), **{})
2016-06-02 12:20:22,371 INFO zen.collector.scheduler: Detailed Task Statistics:
configLoader Current State: FETCHING_MISC_CONFIG Successful_Runs: 1 Failed_Runs: 0 Missed_Runs: 0
Detailed Task States:
configLoader State: RUNNING Total: 1 Total Elapsed: 0.0563 Min: 0.0563 Max: 0.0563 Mean: 0.0563 StdDev: 0.0000
configLoader State: QUEUED Total: 1 Total Elapsed: 0.0003 Min: 0.0003 Max: 0.0003 Mean: 0.0003 StdDev: 0.0000
2016-06-02 12:20:22,372 DEBUG zen.collector.config: Heartbeat timeout set to 900s
2016-06-02 12:20:22,372 DEBUG zen.collector.scheduler: add task configLoader,
2016-06-02 12:20:22,372 DEBUG zen.collector.config: Fetching threshold classes
2016-06-02 12:20:22,379 DEBUG zen.zenperfsnmp: Loading classes ['Products.ZenModel.MinMaxThreshold', 'Products.ZenModel.ValueChangeThreshold']
2016-06-02 12:20:22,380 DEBUG zen.collector.config: Fetching collector thresholds
2016-06-02 12:20:22,448 DEBUG zen.thresholds: Updating threshold ('high event queue', ('localhost collector', ''))
2016-06-02 12:20:22,448 DEBUG zen.thresholds: Updating threshold ('zenmodeler cycle time', ('localhost collector', ''))
2016-06-02 12:20:22,448 DEBUG zen.collector.config: Fetching configurations
2016-06-02 12:20:22,500 ERROR zen.collector.config: Configuration for tor12.ipx unavailable -- is that the correct name
2016-06-02 12:20:22,500 DEBUG zen.collector.scheduler: Task configLoader finished, result: 'Configuration loaded'
2016-06-02 12:20:22,501 DEBUG zen.collector.scheduler: In shutdown stage before
2016-06-02 12:20:22,501 DEBUG zen.collector.scheduler: Removing task configLoader
2016-06-02 12:20:22,501 DEBUG zen.collector.scheduler: tasks to clean KeyedSet([
2016-06-02 12:20:22,501 DEBUG zen.collector.scheduler: Cleanup on task configLoader
2016-06-02 12:20:22,501 DEBUG zen.collector.scheduler: Scheduler._cleanupTaskComplete: result=None task.name=configLoader
2016-06-02 12:20:22,501 DEBUG zen.collector.scheduler: Cleanup on task configLoader
2016-06-02 12:20:22,502 DEBUG zen.collector.scheduler: Scheduler._cleanupTaskComplete: result=None task.name=configLoader
2016-06-02 12:20:22,502 DEBUG zen.zenperfsnmp: Tried to stop reactor that was stopped
2016-06-02 12:20:22,502 INFO zen.zenperfsnmp: Daemon CollectorDaemon shutting down
2016-06-02 12:20:22,503 DEBUG zen.publisher: shutting down
2016-06-02 12:20:22,503 DEBUG zen.publisher: shutting down [publishing]
2016-06-02 12:20:22,503 DEBUG zen.publisher: trying to publish 1 metrics
2016-06-02 12:20:22,504 DEBUG zen.publisher: flushing 1 metrics, current batch size 2
2016-06-02 12:20:22,504 DEBUG zen.publisher: shutting down [publishing]
2016-06-02 12:20:22,508 DEBUG zen.publisher: published 1 metrics to redis
2016-06-02 12:20:22,509 DEBUG zen.publisher: shutting down [disconnecting]
2016-06-02 12:20:22,509 DEBUG zen.publisher: shutting down [disconnected]
2016-06-02 12:20:22,509 INFO zen.publisher: publishing failed: [
2016-06-02 12:20:22,509 INFO zen.publisher: queue still contains 1 metrics
2016-06-02 12:20:22,510 DEBUG zen.zenperfsnmp: Removing service EventService
2016-06-02 12:20:22,510 DEBUG zen.zenperfsnmp: Removing service Products.ZenHub.services.SnmpPerformanceConfig
2016-06-02 12:20:22,510 DEBUG zen.pbclientfactory: Lost connection to localhost:8789 - Connection to the other side was lost in a non-clean fashion: Connection lost.
2016-06-02 12:20:22,511 DEBUG zen.collector.scheduler: In shutdown stage during
2016-06-02 12:20:22,511 DEBUG zen.collector.scheduler: In shutdown stage after
------------------
In the meantime CPU load has decreased again but the alarm is still there.
Attached a screenshot of threshold settings.
Thanks, Martin
| < |
Previous User Issue |
Next Default Apache Host in templet |
> |