Hi everyone, I have some multi-graph reports that show individual lines for each interface I've added to the collection (example attached).

What I actually want is for all the values at each timestamp to be cumulated together and shown like that. For example, if I had 2 interfaces being measured at 12:00pm and one reported 1Mbps while the other 2Mbps for that timestamp....rather than me seeing 1 point at 1Mbps and another at 2Mbps, I want a single point at 3Mbps instead.

I'm sure this is possible....I just don't know how.

Any help appreciated as always :)

http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-73319-15589/450-191/PIX+20130523.png

I have recently switched over to a new domain controller. Now I keep getting could not read the Windows event log and services error in Zenoss. The domain controllers is setup the same way as the old one. I have tried to change the username and password for it and still doesn't work with another username or password. I have checked the COM+ security and added the group that the account is in and still not able to read windows service or event log. Is there somewhere else I'm missing or I can look?

lets see

grep -r "zOracleUser" /opt/zenoss/ZenPacks/

grep -r "zJmxAuthenticante" /opt/zenoss/ZenPacks/

also check threshold calculations and respond with the tales expressions that are being used

Cheers

I am having this same exact problem .. have you fixed it? Are you still having this problem?

Hi.

How add a filter in Event Manager > Commands ?

Device is x.x.x.x

AND  x.x.x.x

AND x.x.x.x

AND not OR

Zenoss 3.2

http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-73296-15585/450-185/zen-filt-50.jpg

So no one is monitoring MS SQL with Zenoss? :(

I'm trying to use JSON/Python API to create a new event

I'm using the documentation (ZenossAPIExample) to create a new event (create_event_on_device)

Up to this point it's working and I am able to create a new event,

The problem is I don't understand how to use the data returns to manage the event,

For example, the return code is:

{u'uuid': u'b8791acb-b6f9-4071-b065-9c26e36acd45', u'tid': 1, u'result': {u'msg'

: u'Created event', u'success': True}, u'action': u'EventsRouter', u'type': u'rp

c', u'method': u'add_event'}

My questions:

1. Is there any way to get the "Event ID" in the return call?

2. What is the "u'uuid'" used for?

All event actions (Acknowledge, close, add note etc..) requires the event ID and I'm trying to sync Zenoss with 3rd party events.

System:

Zenoss: 4.2.3

OS: CentOS 6.4

Any suggestions?

Thanks

Though the discussion went on some time ago, I thought I would add one more possibility to consider.

As an alternative you can also consider using hardware sms gateway. This a kind of device which you buy, put inside a SIM card from your carrier, and connect to LAN. It will send your sms alerts directly to a GSM network. So, your'e independent from your internet connection. Hardware sms gateways are devices that are embedded computers with built-in GSM-modem. They usually operate on Linux, have built-in database and a web server.

Advantages of this approach is surely reliability and less pain with integration. But there are disadvantages too: this costs money. You'll have to make one time investment in such a device.

Just and example of such hardware is SMSEagle

Here you can get Zenoss plugin for it.

Is there a way to assign the needed permissions to some user in order to use zenpack (allow to use the classes defined in the 'check_esx_wbmem.py' file)?

The main problem is that we can't put in the esxi root password into zenoss configs in plain text.

The ValueChangeThreshold is a recent development that arrived (I believe) with Zenoss 4.2. Rather than the administrator having to create a template that checks a MAX and/or a MIN value, this standard template simply checks that the value has "changed" from the last sampling interval.

It is deployed as standard on the ethernetCsmacd and ethernetCsmacd_64 component templates on the ifOperStatusChange threshold.  It is configured to generate a /Status/Perf event when the the value changes, of severity Info.

http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-73268-15581/450-205/ifOperStatusChange_ValueChangeThreshold.jpg

The /Status/Perf Zenoss-supplied event has a transform that checks that a component attribute exists and that the eventKey field matches with the ifOperStatusChange threshold for the ifOperStatus_ifOperStatus datapoint.   If these criteria are met then the event action is set to drop.

Next the status value from the event is compared with the status for this interface in the Zope  configuration Database (ZODB).  If the two are different then the ZODB value is set to match the status detected by the event.                           

http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-73268-15582/450-272/Status_Perf_transform.jpg

zenperfsnmp polls the SNMP OID ifOperStatus every 5 minutes (by default).  Possible values for the operational status (defined in the RFC-1213 MIB and IF-MIB) are:

• 1     Up

• 2     Down
• 3     Testing
• 4     Unknown
• 5     Dormant
• 6     notPresent
• 7     lowerLayerDown

Unfortunately the ValueChangeThreshold threshold type is not a reliable source of events  for interfaces.  This is because other daemons and processes in Zenoss can reset the previous value (strictly the template threshold instance is recreated).  This happens:

• When zenmodeler changes a relevant object
• When any other script (such as an interface monitor / unmonitor script) changes a relevant object in the ZODB database
• When an event transform changes the status of an interface (as in the transform above)
• When the template or object are manipulated by the zendmd testing environment
• When zenping detects an interface change
• When the performance template is changed

The result is a spurious event that changes the value from a previous value of “None” to the current value.  This means that “real” events (eg. changes from Up to Down), may become masked and hence this whole ValueChangeThreshold technique is unreliable.

If an interface changes from Up to Down then zenping (which runs every minute) is more likely to see the interface down before the zenperfsnmp daemon sees it.  zenping changes the status in the ZODB database and a new threshold instance for the ifOperStatusChange threshold, is pushed to the relevant collector (typically the Zenoss server in a Core environment); this new template instance generates an event saying that the status has changed from None to the new status (2 if the interface has gone down) and the "lastValue" of this threshold is set to the new status of down (2). 

At some later stage, the threshold is checked - the value is still down so the ValueChangeThreshold does not fire, even though the last time that zenperfsnmp checked this threshold, the value was 1 (up).

I have tried dropping or closing values that change from None to something - this doesn't help.  The other changes (like zenping) still create a new template instance and still change the lastValue in that template.  The other issue is that if you drop good news events from None to 1 (up) then the bad news never gets closed by the template.  The last Value has been set to 1 (up) so the threshold sees no change.  Further, any "good news" events that don't match a "bad news" event are always silently dropped (standard behaviour, irrelevant whether it is a ValueChangeThreshold event).

After struggling for some time with this quirky behaviour (because it is all time-dependent) I have come to the conclusion that for interfaces at least, you are much safer sticking with the MaxMin threshold.

Cheers,

Jane

Can some one help me the steps to monitor HP Proliant Servers. Which zenpack i should choose?

Please assist.