Of course, nagios plugin will be great. And we should not forget about cacti and munin users here :) Actually, output of already mentioned link ( http://node.example.com:3456/statistics?t=json) can easily be used to retrieve it.
*Sincerely, Oleksandr Drach,* *e-mail: **[email protected]* <[email protected]>*.* 2013/2/26 Peter Secor <[email protected]> > The WUI usually has a pretty good json representation of most screens, > just tack on a query arg ?t=json to the WUI URL and see what you get. I > used to use it a lot when running scripts to check node usage but it's also > useful for scraping other node stats. > > On Feb 25, 2013, at 18:30, Greg Troxel <[email protected]> wrote: > > > > > I would say that two nagios plugins would be useful, and also a status > > tray program. > > > > server plugin: runs on a computer that has an introducer, or a storage > node, > > and returns status of that node locally. > > > > client plugin: runs on a computer that has a client node, and queries it > > (first fix the bug about the CLI being less powerful than the WUI :-) to > > find out if it is connected to introducer and to all servers. > > > > status tray program: probably exactly the client plugin, but > > representing an icon in the local GUI. This could use a new interface > > to get continuous updates from the local client, much like the BSD > > routing socket, or IMAP with the IDLE extension. > > > > I would suggest that firs the CLI be extended to print out what's > > needed, and then the plugins become simple scripts. > > > > Or, perhaps the WUI has a json representation of status. This should be > > relatively easy to do. > > > > > > > > _______________________________________________ > > tahoe-dev mailing list > > [email protected] > > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev > _______________________________________________ > tahoe-dev mailing list > [email protected] > https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev >
_______________________________________________ tahoe-dev mailing list [email protected] https://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev
