On Sun, Dec 13, 2009 at 3:45 PM, Peter Tribble <peter.trib...@gmail.com> wrote:
> On Thu, Dec 10, 2009 at 2:25 AM, Mike Gerdts <mger...@gmail.com> wrote:
>> And on the wishlist
>>
>> - A web service or similar that makes it possible to collect this data
>> or do analysis that spans systems.
>> - API's and tools that can talk to these web services and aid in data
>> visualization.
>
> Now - and this is just a question - what's wrong with snmp, which does
> remote collection from a central station?

There's nothing wrong with that, so long as it fits the overall goals.
 I see "replace sar" as a different problem than "provide more data
through snmp".  When I think of a sar replacement, I think of
something that doesn't require a centralized management infrastructure
to get some sort of historical data.  In order to get historical data
out of most snmp-based solutions, the network management station (the
thing that gets data from the agents) needs to request data from the
agents from time to time.

> Why do you need a web service to collect the data together? I just copy
> it to a central repository and munge it off-host?

I look at a web service as providing a couple different roles.

- In the event that you have a central repository, that central
repository can use the web service to gather data.  If the central
repository is offline or there is some sort of communication problem,
the web service could have the mechanisms to say "give me these
parameters at interval x starting at $starttime until now."

- In the absence of a central repository, a desktop app (or
javascript/flash/javafx hacks in a browser) could query the web
service to gather raw data to visualize it or analyze it.  Perhaps
such an application could simultaneously look at data from multiple
hosts and help with multi-host performance analysis scenarios.

> Why collect this data locally and then serve up the collected data? Why
> not have a kstat daemon that can be queried

Primarily because this doesn't fit the mold of replacing sar.  It
serves a different need that requires more complex infrastructure than
simply enabling a service.

-- 
Mike Gerdts
http://mgerdts.blogspot.com/
_______________________________________________
sysadmin-discuss mailing list
sysadmin-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/sysadmin-discuss

Reply via email to