This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
PerformanceMonitoringHome
(revision 16) (raw view)
---+ Performance Monitoring <table width="100%" align="left" cellspacing="5" style="background-color: white; border: 0pt solid #ffffff" cellpadding="10" border="0"><tbody><tr><td valign="top" style="width: 895px"> *Quick 2.0 links:* %ICON{days}% *[[PmMeetings][ Meetings]]* %ICON{bubble}% *[[http://open-services.net/pipermail/oslc-pm_open-services.net][Email archives]]* %ICON{sitetree}% *[[PmScenariosV2][PM Scenarios]]* %ICON{book}% *[[PmSpecificationV2][PM Specification]]* %ICON{info}% *[[PmExamples][Examples]]* %TOC% ---++ Goal Enable simpler, more open, more durable integration between monitoring tools and consumers of monitoring data about resources such as applications, computer systems, storage volumes, etc. ---+++ To join this working group Please: 1 Request a meeting invitation: contact [[JulianneBielski][Julie Bielski]] or [[mailto:oslc-pm-owner@open-services.net][send an email to the working group's mailing list admins]] (note: remove NOSPAM from the destination domain name). 1 [[http://open-services.net/mailman/listinfo/oslc-pm_open-services.net][Register for the Performance Monitoring mailing list]] ---++ Background This working group will define a common set of resources, formats and [[http://en.wikipedia.org/wiki/Restful][RESTful]] services that usable by lifecycle tools such as operation dashboards, applications, and products to monitor resources. The need for this workgroup is further driven by [[http://en.wikipedia.org/wiki/Web_operations][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 iterations such as storage, network, computer system, etc. ---++ Specifications <blockquote> %RED%2.0 is the first version of the documents below. The OSLC Core working group recommends that domain working groups use the specification version to indicate that they are based on the [[OslcCoreSpecification][OSLC Core 2.0]] specification. This working group chose to use a consistent version number for all related documents. %ENDCOLOR% </blockquote> ---+++ 2.0 (Draft) OSLC-PM 2.0 Specifications | *Document* | *2.0* || | | *Link* | *Status* | | Performance Monitoring Specification | [[PmSpecificationV2][2.0]] | =Initial Draft= | ---+++ Supporting Documents | *Document* | *2.0* || | | *Link* | *Status* | | PM Scenarios and Use Cases | [[PmScenariosV2][2.0]] | =Note= | | PM Vocabulary | [[PmVocabulary][2.0]] | =Initial Draft= | | Common Resource Type Vocabulary | [[CrtVocabulary][2.0]] | =Proposal= | | Architectural Direction | [[PmArchitecturalDirectionV2][2.0]] | =Note= | | Examples | [[PmExamples][2.0]] | =Note= | ---++ Milestones Note: iterative specification validation will be occurring as the drafts evolve before finalization. The goal is to have at least 2 implementations of the specification before it is considered finalized. | *Version* | *Create Draft Specs* | *Start Convergence* | *Finalize Specs* || | 2.0 | 2012-05-15 | 2012-06-15 | 2012-08-15 || </td><td valign="top" style="width: 250px"> ---++++!! Participants | <p> [[PratikGupta][Pratik Gupta]] (co-lead) <br />[[JulianneBielski][Julie Bielski (co-lead)]]</p><p>[[JohnArwe][John Arwe]]</p><p> [[JoeRoss][Joe Ross]]</p><p> [[JacobYackenovich][Jacob Yackenovich]]</p><p> [[TuanDang][Tuan Dang]]</p><p>Donald Cronin</p><p>Shepherd Shi</p><p>David Cox</p><p> [[MichaelMorton][Michael Morton]]</p><p>[[MichaelFiedler][Michael Fiedler]]</p><p> [[SteveSpeicher][Steve Speicher]]</p><p>Scott Donohoo</p><p> [[Jim Conallen]]</p><p>Tod Thorpe</p><p> [[JohnTobasco][John Tobasco]]</p> | <p>IBM</p> | | [[DavidHarrison][David Harrison]] | TIETO | ---++++!! Resources [[http://open-services.net/participate/][How to join a working group]] [[PmMeetings][Meeting Agendas and Minutes]] ---++++!! Mailing List [[http://open-services.net/mailman/listinfo/oslc-pm_open-services.net][Register for the Performance Monitoring mailing list]] [[http://open-services.net/pipermail/oslc-pm_open-services.net][ Performance Monitoring mail archives]] [[http://open-services.net/mailman/listinfo/community_open-services.net][General OSLC Community]] </td></tr></tbody></table>
Edit
|
Attach
|
P
rint version
|
H
istory
:
r18
<
r17
<
r16
<
r15
<
r14
|
B
acklinks
|
V
iew topic
|
Raw edit
|
More topic actions...
Topic revision: r16 - 16 Jul 2012 - 14:32:50 -
LeeReamsnyder
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback