Device Issues Portlet blank

Discussion:

Photon

2013-10-02 17:27:42 UTC

Photon [http://community.zenoss.org/people/Photon] created the discussion

"Device Issues Portlet blank"

To view the discussion, visit: http://community.zenoss.org/message/74819#74819

--------------------------------------------------------------
Hi every1,

Â We've had an issue with the device issues portlet ever since we installed 4.2.4 and the SP71 patch. The porlet is now blank. We tried to follow its source code to see where it would lead us. In */opt/zenoss/Products/ZenWidgets/browser/Portlets.py,* we found these lines (inside getDeviceDashboard method which is called by getDeviceIssuesJSON) :
*zep = getFacade('zep')*
*...*
*deviceSeverities = zep.getDeviceIssuesDict()*

By using zendmd and executing these lines :
*from Products.Zuul import getFacade*
*zep = getFacade('zep')*
*deviceSeverities = zep.getDeviceIssuesDict()*
*deviceServerities.viewitems()*
we get an empty dict. On the other hand, using *zep.getEventSummariesGenerator()*, we can extract all current events.
The Root Organizer portlet isn't empty and extracts correctly events.

Any idea on why we're having this issue ?

Thanks in advance.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74819#74819]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

Eric Gemme

2013-10-11 11:13:28 UTC

Permalink

Hrvoje Tolic

2013-10-16 06:47:16 UTC

Permalink

Hrvoje Tolic [http://community.zenoss.org/people/htolic] created the discussion

"Re: Device Issues Portlet blank"

To view the discussion, visit: http://community.zenoss.org/message/74968#74968

--------------------------------------------------------------
I opened a bug ticket on jira here http://jira.zenoss.com/jira/browse/ZEN-8721 http://jira.zenoss.com/jira/browse/ZEN-8721
I also enclosed my fix to the bug. It is working for me. I hope it doesn't break any other things. In the fix I use helper python list devprocessed which might not be the most efficient way to do it. The fix roams through events and there are usually multiple events per device and using this list I keep track of devices that I already processed so duplicates don't show up on Device Issues portlet.

Here's the code for the fix:

diff --git a/Products/ZenWidgets/browser/Portlets.py b/Products/ZenWidgets/browser/Portlets.py
index de28299..beb3fed 100644

--- a/Products/ZenWidgets/browser/Portlets.py
+++ b/Products/ZenWidgets/browser/Portlets.py

@@ -19,12 +19,15 @@ from Products.Zuul import getFacade
from Products.ZenEvents.HeartbeatUtils import getHeartbeatObjects
from zenoss.protocols.services import ServiceException
from zenoss.protocols.services.zep import ZepConnectionError
+from zenoss.protocols.jsonformat import from_dict
+from zenoss.protocols.protobufs.zep_pb2 import EventSummary
from Products.ZenUtils.guid.interfaces import IGUIDManager
from Products.ZenUtils.jsonutils import json
from Products.ZenUtils.Utils import nocache, formreq, extractPostContent
from Products.ZenWidgets import messaging
from Products.ZenModel.Device import Device
from Products.ZenModel.ZenossSecurity import *
+from Products.ZenEvents.events2.proxy import EventSummaryProxy
from Products.ZenEvents.browser.EventPillsAndSummaries import \
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â getDashboardObjectsEventSummary, \
Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ObjectsEventSummary,Â Â Â \

@@ -183,27 +186,34 @@ class DeviceIssuesPortletView(BrowserView):
Â Â Â Â def getDeviceDashboard(self):
Â Â Â Â Â Â Â Â """return device info for bad device to dashboard"""
Â Â Â Â Â Â Â Â zep = getFacade('zep')
+Â Â Â Â Â Â Â zep_filter = zep.createEventFilter(status=[0,1], severity=[3,4,5], details={'zenoss.device.production_state':1000})
Â Â Â Â Â Â Â Â manager = IGUIDManager(self.context.dmd)
-Â Â Â Â Â Â Â deviceSeverities = zep.getDeviceIssuesDict()
Â Â Â Â Â Â Â Â zem = self.context.dmd.ZenEventManager

Â Â Â Â Â Â Â Â devdata = []
-Â Â Â Â Â Â Â for uuid in deviceSeverities.keys():
-Â Â Â Â Â Â Â Â Â Â Â dev = manager.getObject(uuid)
-Â Â Â Â Â Â Â Â Â Â Â if dev and isinstance(dev, Device):
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â if (not zem.checkRemotePerm(ZEN_VIEW, dev)
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â or dev.productionState < zem.prodStateDashboardThresh
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â or dev.priority < zem.priorityDashboardThresh):
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â continue
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â alink = dev.getPrettyLink()
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â try:
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â severities = deviceSeverities[uuid]
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â severities = dict((zep.getSeverityName(sev).lower(), counts) for (sev, counts) in severities.iteritems())
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â pill = getEventPillME(dev, severities=severities)
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â except ServiceException:
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â continue
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â evts = [alink,pill]
-Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â devdata.append((evts, severities))
+Â Â Â Â Â Â Â devprocessed = []
+Â Â Â Â Â Â Â for summary in zep.getEventSummariesGenerator(filter=zep_filter):
+Â Â Â Â Â Â Â Â Â Â Â evt = EventSummaryProxy(from_dict(EventSummary, summary))
+Â Â Â Â Â Â Â Â Â Â Â try:
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â uuid = summary['occurrence'][0]['actor']['element_uuid']
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â dev = manager.getObject(uuid)
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â if dev and isinstance(dev, Device) and evt.device not in devprocessed:
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â if (not zem.checkRemotePerm(ZEN_VIEW, dev)
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â or dev.productionState < zem.prodStateDashboardThresh
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â or dev.priority < zem.priorityDashboardThresh):
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â continue
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â alink = dev.getPrettyLink()
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â try:
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â severities = zep.getEventSeveritiesByUuid(uuid)
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â severities = dict((zep.getSeverityName(sev).lower(), counts) for (sev, counts) in severities.iteritems())
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â pill = getEventPillME(dev, severities=severities)
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â except ServiceException:
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â continue
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â evts = [alink,pill]
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â devdata.append((evts, severities))
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â devprocessed.append(evt.device)
+Â Â Â Â Â Â Â Â Â Â Â except KeyError:
+Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â continue
Â Â Â Â Â Â Â Â devdata.sort(key=lambda x:(x[1]['critical'], x[1]['error'], x[1]['warning']), reverse=True)
Â Â Â Â Â Â Â Â return [x[0] for x in devdata[:100]]
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74968#74968]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

Eric Gemme

2013-10-17 22:29:12 UTC

Permalink

Eric Gemme [http://community.zenoss.org/people/egemme] created the discussion

"Re: Device Issues Portlet blank"

To view the discussion, visit: http://community.zenoss.org/message/74979#74979

--------------------------------------------------------------
Hrvoje,Â I can't see you Jira ticket.Â Â Is it gone?Â Â I wanted to see if someone picked it up for evaluation.

As I look at you fix,Â I think someone must have broken some typical input for the issues portlet in SP71.Â Â So prior to apply your fix,Â I would like to know if the input in question is gone forever because it became deprecated,Â or someone really goofed on this one and could be restored shortly.Â Â In the latter case,Â I will wait for a more permanent fix.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74979#74979]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

Hrvoje Tolic

2013-10-18 07:25:12 UTC

Permalink

Hrvoje Tolic

2013-10-25 08:05:41 UTC

Permalink

Eric Gemme

2013-10-25 13:03:42 UTC

Permalink

Hrvoje Tolic

2013-10-25 13:05:51 UTC

Permalink