What kind of statistics can be collected in-world?

Hi there,
There is a lot of cool and interesting information in the SL viewer's statistics window such as FPS, bandwidth usage etc (http://wiki.secondlife.com/wiki/Help:Simulator_statistics). Is there any way to use LSL to create an object that can pull some of this information out for analysis / aggregation?

My initial thoughts were that these numbers can only be grabbed at the viewer level and aren't relevant to in-world, but LSL does offer some statistical functions like llGetRegionFPS, so I thought I'd field the question to the scripting pros out there. Is there only limited numbers available via LSL, or is this a work-in-progress feature to be able to pull this information from LSL?

Enlighten me. )

Cheers,
LL

I think it's just a few basic stats that are available to LSL. Region FPS, time dilation.. With it's limited memory and lack of any real scheduling capabilities, LSL isn't that great for doing status tracking - that's something better suited to a bot.

So libsecondlife (http://www.libsecondlife.org/wiki/Main_Page) provides the functionality to pull this information out s bot? I'm assuming you are referring to that library when you say a bot is the best way to go?

It depends on when you want to collect the info. If you want something that sits at your home and measures sim performance 24/7, libsl is probably the way to go. If you want something that's somehow interacting with you when you're logged in based on how your current sim is doing, you're probably better modding the open source viewer.

It would nice to collect my data two ways. One as a bot that sits on my land and just logs the performance, so libsl would probably be fine for that. I would also like to monitor my own personal performance too though, which obviously changes depending on where I am at. Could a libsl bot be attached to me that follows me around recording the statistics of whatever parcel I am in?

If an equivalent to an attachable prim can be developed using libsl then that would work fine. Obviously if somebody created a plugin arch for the viewer this would be much easier.

You could probably have a libsl bot that follows you around but I bet it would be a lot easier to just find where in the viewer code the stats are done and put whatever you want there. The lag monitor stuff under the help menu is probably a good place to start since it already looks at stats and sorta sums up the results via a few traffic lights.

Hmmm... diving into the viewers guts isn't exactly my idea of a fun time, and doesn't allow for easy distribution of my work. We really need a plugin architecture for this to happen, realistically. (