[oslc] Fw: Proposal for Performance Monitoring Workgroup

[Robert W Myers]

ROCR is also concerned  with performance issues (if any) related to 150 
Friendships.
Thank you,
Bob




From:   Steve K Speicher/Raleigh/IBM at IBMUS
To:     community at open-services.net
Cc:     Donald Cronin/Raleigh/IBM at IBMUS
Date:   02/08/2012 12:20 PM
Subject:        [oslc] Fw: Proposal for Performance Monitoring Workgroup
Sent by:        community-bounces at open-services.net



Forwarding proposal to Community for additional feedback.

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645

> From: Donald Cronin/Raleigh/IBM at IBMUS
> To: oslc-core at open-services.net, 
> Cc: Julianne Bielski/Raleigh/IBM at IBMUS, Pratik Gupta/Raleigh/IBM at IBMUS
> Date: 02/01/2012 01:32 PM
> Subject: [oslc-core] Proposal for Performance Monitoring Workgroup
> Sent by: oslc-core-bounces at open-services.net
> 
> We would like to propose a new working group entitled Performance 
Monitoring.
> 
> The goal of this workgroup is to define a common set of resource 
definitions
> and RESTful services that can be used by lifecycle tools such as 
operational
> dashboards, applications, and products to monitor resources. The need 
for 
> this workgroup is further driven by web operations 
http://en.wikipedia.org/
> wiki/Web_operations .
> 
> Monitored resource definitions define the data about entities like 
> applications, computer systems, storage volumes, etc. commonly used to 
> observe a coarse-grained summary of a monitored resource's state, e.g. 
its 
> self-reported health. Some monitoring tools collect hundreds or more 
> individual metrics about a range of resources, it is NOT our intent to 
> reproduce that work in all its richness and detail. Only the subset 
needed 
> to satisfy the in-scope scenarios will be included in the resource 
> definitions, i.e. the subset that most/all tools would be able to 
provide 
> and that participants can readily agree on. The approach will be to 
define a
> small number of tightly constrained scenarios, address those by drafting 


> specifications, collect implementation experience using those drafts, 
and 
> then close (finalize) those specifications. This will decrease the 
barrier 
> to sharing monitored data across multiple vendors and tools as part of 
the 
> Operations Lifecycle. Future iterations of that process may be used to 
> address additional scenarios and resource types.
> 
> The initial focus will be on application monitoring. This is a key 
resource 
> type today. There are many other areas of monitoring that could be 
covered 
> in the future such as storage, network, computer system, etc. The 
workgroup 
> will be led by Pratik Gupta and Julianne Bielski.
> 
> Steve Speicher could you please add this to the next Core agenda. 
> 
> Thanx
> 
> Regards,
> 
> Donald Cronin
> Program Director, Tivoli Technical Strategy and Architecture
> IBM Software Group 
> 
> [image removed] 
> 
> Phone: 1-919-224-1452 | Mobile: 1-919-426-5241
> E-mail: dcronin at us.ibm.com
> 
> [image removed] 
> 
> 3901 S Miami Blvd
> Durham, NC 27703-9135
> United States
> 
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net


_______________________________________________
Community mailing list
Community at open-services.net
http://open-services.net/mailman/listinfo/community_open-services.net


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/community_open-services.net/attachments/20120208/ff0bd035/attachment-0003.html>