[Oslc-pm] scenario that describes the administering of a monitoring resource

[John Arwe]

Sounds reasonable enough to me.  "Can we" probably boils down to an 
implementation feedback question.  In order for the content it drives to 
be in the spec, we would need producer(s) and consumer(s) in order to 
finalize.  If you have the ability to do that prototyping work to provide 
feedback, then that base would be covered.  If you don't we'd need to see 
if anyone else can cover it; if not, any content driven purely by that 
scenario would have to be deferred.  "Should we" is a matter of scope: 
time and effort, under the assumption that "can" is answered positively.
I'll ask around and see if we have anyone with expertise in this area who 
can participate.

Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario




From:   <David.Harrison at tieto.com>
To:     <oslc-pm at open-services.net>
Date:   05/09/2012 04:46 AM
Subject:        [Oslc-pm] scenario that describes the administering of a 
monitoring      resource
Sent by:        oslc-pm-bounces at open-services.net



Hi,
 
Should we have a scenario that describes the administering of a monitoring 
resource ?
 
Example for JVM monitoring.(ref JSR 174)
 
Health Indicators 
Class load/unload 
Memory allocation statistics 
Garbage collection statistics 
Monitor info & statistics 
Thread info & statistics 
Just-in-Time statistics 
Object info (show/count all objects in the Java heap) 
Underlying OS and platform info 
etc.
 
Run-Time Control 
Minimum heap size 
Verbose GC on demand 
Garbage collection control 
Thread creation control 
Just-in-Time compilation control 
etc. 
 
Designed with the following characteristics: 
 
Very low performance impact, even when events are being monitored 
……….. etc
 
David Harrison
Software Architect, Networks R&D

Tieto Sweden AB
Phone:+46 (0)10 48 17435
Mobile: +46 (0)722 160924


 
 
 
 _______________________________________________
Oslc-Pm mailing list
Oslc-Pm at open-services.net
http://open-services.net/mailman/listinfo/oslc-pm_open-services.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-pm_open-services.net/attachments/20120509/8e71f971/attachment-0003.html>