some mundane, some not....

   A dozen of these boxes have failed of late, with power supply failures.
How many more of these do I have in my environment, and where?  (best if
Zenoss realized on its own that 5% of boxes of this type have shown this
issue :) is that pie in the sky?))

   Basic notes to go along with the status information - IE, Zenoss detects
device is down at site y.   Helpdesk opens a troubleticket (troubleticket
within Zenoss would be nice, but assuming an external ticketing?) There
should be basic notes within Zenoss - the ticket number, assigned engineer,
expected time to recover, etc. on a public dashboard, maybe


   allow capture additional manual information - IE, curcuit ids for
networks, contact information for a site, device, or application?

   I haven't looked, but, does Zenoss support the concept of application
monitoring, seperate from device monitoring?  IE, an app might consist of
some web servers, a database server, some specialized software (non standard
ports, maybe?)  If some part of the app has a failure, the notification
might be different then for the device...

Templating wuld be nice - IE, I have 50 or so exchange servers.   Monitor
all of these on every exchange server...

Mactrack (see NetDisco, NAV)
Integrated IP mangement (see ipplan (sourceforge) metaip (commercial)),



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Duncan McGreggor
Sent: Saturday, August 12, 2006 12:22 PM
To: Zenoss Users
Subject: [zenoss-users] How would you *like* to use Zenoss?
[Spam][98.5%]


As we all know, this list is mainly dedicated to learning about using
Zenoss. But in this thread, I'd like to encourage some wish-list
talk :-)

I've been pondering web services, mashup applications, and Zenoss...
and this got me thinking about the business possibilities potentially
available to users. Thus the subject of this email :-)

How would you *like* to use Zenoss?

By this I mean something along the following lines:

* The web views of zenoss represent a MASSIVE investment of your
company -- all that hardware and the software running on those systems.
* Zenoss provides a view of that investment; in particular, device
metadata and event information for your networked hardware and software
* In addition to being monitoring software, Zenoss is management
software, therefore...
* What else to you want to manage? What other information do you want
know about your company's networked investment? What related
information do you want to be able to manipulate? What related tasks
do you want to perform?

Let me give some examples to get you thinking along these lines:

Example 1:
Charlie manages 2000 servers in a low-budget hosting environment. She
has been tasked with maintaining the equipment at super-low costs,
the preferred method of which is eBay purchases. Since any device
failure could be the last, when a device fails, she would like to see
the average eBay cost for that same piece of equipment. eBay provides
an API for just these kinds of queries.

Example 2:
On IRC and in a ticket (#259), giesen suggested that Zenoss provide
voice alert capability. Admins could then get a phone message for
events they were interested in. There is a web service that provides
just such a service (subscription-based), and could be integrated
into Zenoss as a mashup.

Example 3:
John manages customer applications in data cetners all over the
United States, Europe, and Asia. If something goes wrong with an
application, he wants to have a visual representation of its location
in an instant so he doesn't have to waste time thinking about where
it is. Google maps provides an API to do just this sort of thing.

Example 4:
Ng has a small monitoring facility in Vietnam with zenoss instances
running small virtual servers. However, the hosting company charges a
great deal for disk space, and he'd like to save where he can.
Particularly, he only needs a few MIB files and doesn't want all of
them to be bundled with Zenoss. Ng would like Zenoss to provide a web
service for retrieving MIB files automatically and as-needed only.

So, with these in mind, what other business processes could Zenoss
make easier? Given that you are either already managing your
networked resources with Zenoss or are thinking about it, the
integration of various useful web services into Zenoss could 1) make
your lives that much easier, and/or 2) save your company that much
more money.

And feel free to post completely off-the-wall ideas -- we want to
stimulate creative solutions here :-)

Thanks!

d
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to