Monitoring Module
From OpenSimulator
(→Retrieved data) |
(→Retrieved data) |
||
Line 50: | Line 50: | ||
= Retrieved data = | = Retrieved data = | ||
+ | |||
+ | == General == | ||
+ | {| border="1" | ||
+ | ! Stat name !! Descriptoin | ||
+ | |- | ||
+ | | AgentCountMonitor || Number of avatars in the region. | ||
+ | |- | ||
+ | | ChildAgentCountMonitor || Number of child agents in the region. These are used by viewers with avatars in neighbouring regions in order to see into and effect the neighbouring region. | ||
+ | |- | ||
+ | | GCMemoryMonitor || Amount of memory currently allocated to the virtual machine garbage collector. | ||
+ | |- | ||
+ | | ObjectCountMonitor || Number of prims in the region. | ||
+ | |} | ||
+ | |||
+ | '''More to follow''' | ||
+ | |||
+ | == Physics == | ||
+ | |||
+ | The following physics stats are always present. | ||
+ | |||
+ | {| border="1" | ||
+ | | PhysicsFrameMonitor || Obsolete. Same as PhysicsFrameTimeMonitor | ||
+ | |- | ||
+ | | PhysicsFrameTimeMonitor || Average amount of time taken by physics processing per frame | ||
+ | |} | ||
+ | |||
+ | '''More to follow''' | ||
+ | |||
== Examples == | == Examples == | ||
=== OpenSimulator 0.7.2 and earlier === | === OpenSimulator 0.7.2 and earlier === |
Revision as of 16:13, 4 June 2012
Contents |
Introduction
This facility provides a way to retrieve data per region.
Enabling
In OpenSimulator 0.7.2 it is always active. In current development code it is active by default but can be disabled by setting
[Monitoring] Enabled = false
Retrieving data
OpenSimulator 0.7.2 and earlier
In OpenSimulator 0.7.2 and earlier, each region will register a URL on the built-in OpenSimulator HTTP server with the format
/monitorstats/<region-uuid>
If you type
show http-handlers
on the region console you'll see something like this in the HTTP section
/monitorstats/dd5b77f8-bf88-45ac-aace-35bd76426c81 /SStats/ /CAPS/VS/ regionImagedd5b77f8bf8845acaace35bd76426c81 /monitorstats/dd5b77f8-bf88-45ac-aace-35bd76426c82 regionImagedd5b77f8bf8845acaace35bd76426c82
where the UUID following monitorstats corresponds to the region ID.
OpenSimulator development code
In OpenSimulator development code, the region data can also be accessed via region name. Therefore, typing
show http-handlers
will return something like
/monitorstats/dd5b77f8-bf88-45ac-aace-35bd76426c81 /monitorstats/test /SStats/ /CAPS/VS/ regionImagedd5b77f8bf8845acaace35bd76426c81 /monitorstats/dd5b77f8-bf88-45ac-aace-35bd76426c82 /monitorstats/test2 regionImagedd5b77f8bf8845acaace35bd76426c82
where the data can also be retrieved via region name (test and test2).
Retrieved data
General
Stat name | Descriptoin |
---|---|
AgentCountMonitor | Number of avatars in the region. |
ChildAgentCountMonitor | Number of child agents in the region. These are used by viewers with avatars in neighbouring regions in order to see into and effect the neighbouring region. |
GCMemoryMonitor | Amount of memory currently allocated to the virtual machine garbage collector. |
ObjectCountMonitor | Number of prims in the region. |
More to follow
Physics
The following physics stats are always present.
PhysicsFrameMonitor | Obsolete. Same as PhysicsFrameTimeMonitor |
PhysicsFrameTimeMonitor | Average amount of time taken by physics processing per frame |
More to follow
Examples
OpenSimulator 0.7.2 and earlier
On OpenSimulator 0.7.2 and earlier, fetching
http://192.168.1.2:9000/dd5b77f8-bf88-45ac-aace-35bd76426c81
will return something like
<?xml version="1.0"?> <data> <AgentCountMonitor>0</AgentCountMonitor> <ChildAgentCountMonitor>0</ChildAgentCountMonitor> <GCMemoryMonitor>32358400</GCMemoryMonitor> <ObjectCountMonitor>0</ObjectCountMonitor> <PhysicsFrameMonitor>0</PhysicsFrameMonitor> <PhysicsUpdateFrameMonitor>0</PhysicsUpdateFrameMonitor> <PWSMemoryMonitor>354172928</PWSMemoryMonitor> <ThreadCountMonitor>0</ThreadCountMonitor> <TotalFrameMonitor>1</TotalFrameMonitor> <EventFrameMonitor>0</EventFrameMonitor> <LandFrameMonitor>0</LandFrameMonitor> <LastFrameTimeMonitor>87</LastFrameTimeMonitor> </data>
OpenSimulator 0.7.3 and later
In current development code, more statistics have been added, so instead you'll see something like
<?xml version="1.0"?> <data> <AgentCountMonitor>0</AgentCountMonitor> <ChildAgentCountMonitor>0</ChildAgentCountMonitor> <GCMemoryMonitor>32358400</GCMemoryMonitor> <ObjectCountMonitor>0</ObjectCountMonitor> <PhysicsFrameMonitor>0</PhysicsFrameMonitor> <PhysicsUpdateFrameMonitor>0</PhysicsUpdateFrameMonitor> <PWSMemoryMonitor>354172928</PWSMemoryMonitor> <ThreadCountMonitor>0</ThreadCountMonitor> <TotalFrameMonitor>1</TotalFrameMonitor> <EventFrameMonitor>0</EventFrameMonitor> <LandFrameMonitor>0</LandFrameMonitor> <LastFrameTimeMonitor>87</LastFrameTimeMonitor> <TimeDilationMonitor>1</TimeDilationMonitor> <SimFPSMonitor>56.6666679382324</SimFPSMonitor> <PhysicsFPSMonitor>46.9475212097168</PhysicsFPSMonitor> <AgentUpdatesPerSecondMonitor>0</AgentUpdatesPerSecondMonitor> <ActiveObjectCountMonitor>0</ActiveObjectCountMonitor> <ActiveScriptsMonitor>0</ActiveScriptsMonitor> <ScriptEventsPerSecondMonitor>0</ScriptEventsPerSecondMonitor> <InPacketsPerSecondMonitor>0</InPacketsPerSecondMonitor> <OutPacketsPerSecondMonitor>0</OutPacketsPerSecondMonitor> <UnackedBytesMonitor>0</UnackedBytesMonitor> <PendingDownloadsMonitor>0</PendingDownloadsMonitor> <PendingUploadsMonitor>0</PendingUploadsMonitor> <TotalFrameTimeMonitor>0</TotalFrameTimeMonitor> <NetFrameTimeMonitor>0</NetFrameTimeMonitor> <PhysicsFrameTimeMonitor>0</PhysicsFrameTimeMonitor> <SimulationFrameTimeMonitor>0</SimulationFrameTimeMonitor> <AgentFrameTimeMonitor>0</AgentFrameTimeMonitor> <ImagesFrameTimeMonitor>0</ImagesFrameTimeMonitor> </data>