Okey dokey - my sflow/netflow request is unlikely to make it to 2.3 so I've compiled a list of things that as far as I'm aware I can't do now but would like to be able to do. Hopefully I'm not getting too ambitious. Some have been mentioned already and some may be in trac but here goes anyway (in no particular order).
1. A systray/widget for windows/mac/linux to show a simple overview - clicks take you to the relevant page on the web gui. Could be a simple RSS feed type thing. 2. Manual editing and overrides of the discovered network topology and fix the duplicate network issues (subnet is a subnet of itself) 3. Ability to add templates and zProperties to a product or manufacturer class 4. Where a product class is not detected by SNMP but the manufacturer is, why not add the device to the manufacturer class as unknown. 5. Ability to email people that do not necessarily have accounts on the zenoss server - for instance, I want to send an email to a non-technical manager when toner is low on a laser printer or mail a group of users if some other device/system is down. 6. Ability to drill down from the network map. 7. Notifications via XMPP/IM etc or a transport-independent abstraction layer for notifications that is as easy as possible to build notification plugins for. 8. A bit more point and click for basic customisation - I'm amazed that the MIB browser Zenpack was not part of core a long time ago (I reckon that the MIB browser should be available for selecting custom perf monitors too). This kind of thing would also be great for syslog data mapping and classification. 9. Consistent, up-to-date documentation that is in one place and goes into more detail for those that want to do a bit of customisation but who haven't a clue about python and can't read source code. 10. Grabbing properties from SNMP that are not necessarily performance or availability metrics such as serial number, firmware version, again, selectable via the gui using the mib browser zenpack. At the very least, being able to view custom properties that are manually edited on the main view for a device (or network or device class or location etc etc). 11. Use of textual conventions from manufacturer MIB files - this could also be used to automatically populate the products and for adding other fields as described in point 10. While I'm here, and I know this is only going to make v3000 if at all, but think of all the MSPs that you could please by having a probe/agent/proxy that could be installed at a customers site (windows), which reports back to a NOC using one-way ssl connections. It's what many of the big MSP platforms do and could win Zenoss a lot of business by capturing startup MSPs with core before they get big. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=22781#22781 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
