Discussion:
Device Issues dashboard portlet remains empty
nilie
2012-08-29 18:03:54 UTC
Permalink
nilie [http://community.zenoss.org/people/nilie] created the discussion

"Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
It's not like a show stopper but you know how managers crave for cool dashboards and fancy reports so did anyone encounter this problem in fresh install of Zenoss Core v4.2 ? If not, anything that I should consider or verify ?


Thanks.
--------------------------------------------------------------

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

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
OneLoveAmaru
2012-08-29 18:37:29 UTC
Permalink
OneLoveAmaru [http://community.zenoss.org/people/OneLoveAmaru] created the discussion

"Re: Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
What issues are you showing under Events?
--------------------------------------------------------------

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

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
nilie
2012-08-29 18:57:00 UTC
Permalink
nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
I would like to see names of devices that have associated one or more events of severity error and higher like in the event console.
--------------------------------------------------------------

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

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
OneLoveAmaru
2012-08-29 19:26:44 UTC
Permalink
OneLoveAmaru [http://community.zenoss.org/people/OneLoveAmaru] created the discussion

"Re: Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
What issues are you showing under Events at this moment?
--------------------------------------------------------------

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

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
nilie
2012-08-30 18:30:47 UTC
Permalink
nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
I couldn't find a way to attach a screenshot with my reply but in my Event Console I have the following :

2 devices with critical (red) events
4 devices with error (orange) events
12 devices with warning (yellow) events

and the Device Issues portlet is still empy.
--------------------------------------------------------------

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

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
nilie
2012-09-06 14:31:43 UTC
Permalink
nilie [http://community.zenoss.org/people/nilie] created the discussion

"Re: Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
The mistery has been solved!
The events displayed in the Event Console were caused by syslog messages received from devices that were not defined/discovered in Zenoss. The Device Issues dashboard portlet is being populated *only when a device that has beed added to Zenoss* is the source of an event. So Zenoss works as designed, it was my mistake.
--------------------------------------------------------------

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

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
dimiko
2013-10-10 07:51:40 UTC
Permalink
dimiko [http://community.zenoss.org/people/dimiko] created the discussion

"Re: Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
I have similar problems. The difference is I have already added these devices to Zenoss.

Did a fresh install of Zenoss Core 4.2.4 and although I see some error & critical events in Event Console none of these appear in the Device Issues portlet. The devices in question have Production State: Production.
--------------------------------------------------------------

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

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
Jared Ready
2013-10-14 17:39:55 UTC
Permalink
Jared Ready [http://community.zenoss.org/people/residentbiscuit] created the discussion

"Re: Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
Similar issue here. Only 9 devices are showing up in this portlet. No critical events are being shown here at all.
--------------------------------------------------------------

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

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-16 06:46:14 UTC
Permalink
Hrvoje Tolic [http://community.zenoss.org/people/htolic] created the discussion

"Re: Device Issues dashboard portlet remains empty"

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

--------------------------------------------------------------
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.
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,    \
         """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 = []
-            dev = manager.getObject(uuid)
-                if (not zem.checkRemotePerm(ZEN_VIEW, dev)
-                    or dev.productionState < zem.prodStateDashboardThresh
-                    continue
-                alink = dev.getPrettyLink()
-                    severities = deviceSeverities[uuid]
-                    severities = dict((zep.getSeverityName(sev).lower(), counts) for (sev, counts) in severities.iteritems())
-                    pill = getEventPillME(dev, severities=severities)
-                    continue
-                evts = [alink,pill]
-                devdata.append((evts, severities))
+        devprocessed = []
+            evt = EventSummaryProxy(from_dict(EventSummary, summary))
+                uuid = summary['occurrence'][0]['actor']['element_uuid']
+                dev = manager.getObject(uuid)
+                    if (not zem.checkRemotePerm(ZEN_VIEW, dev)
+                        or dev.productionState < zem.prodStateDashboardThresh
+                        continue
+                    alink = dev.getPrettyLink()
+                        severities = zep.getEventSeveritiesByUuid(uuid)
+                        severities = dict((zep.getSeverityName(sev).lower(), counts) for (sev, counts) in severities.iteritems())
+                        pill = getEventPillME(dev, severities=severities)
+                        continue
+                    evts = [alink,pill]
+                    devdata.append((evts, severities))
+                    devprocessed.append(evt.device)
+                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/74967#74967]

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