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.
OSLC_logo.png

Open Services for Lifecycle Collaboration
Performance Monitoring Vocabulary

Status: Under Construction wip Draft covering 2.0 Scenarios - 2 May 2012

NOTE: This version of the specification has version 2.0 to indicate that it is an OSLC Core 2.0 compliant specification. This specification is the initial version of an OSLC Performance Monitoring specification.

This Version

Latest Version PreviousVersion
  • N/A
Authors

Contributors

Table of Contents

License

88x31.png
This work is licensed under a Creative Commons Attribution License.

Notation and Conventions

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC2119. Domain name examples use RFC2606.

Introduction

(this section is informative)

This specification builds on the OSLC Core Specification to define the resources and operations supported by an Open Services for Lifecycle Collaboration (OSLC) Performance Monitoring provider.

Performance Monitoring resources define records whose content is most useful in the operational stage of the software development, test and deployment lifecycle. They represent individual resources as well as their relationships to other resources and to other linked resources outside of the Performance Monitoring domain. The intent of this specification is to define the set of HTTP-based RESTful interfaces in terms of HTTP methods: GET, POST, PUT and DELETE, HTTP response codes, MIME type handling and resource formats. The capabilities of the interface definitions are driven by key integration scenarios and therefore don't represent a complete setup of operations on resources or resource types. The resource formats and operations may not match exactly the native models supported by existing implementations but are intended to be compatible with them.

Performance Monitoring, as referenced in this specification, refers to the collection of data about IT systems such as servers, workstations, services, and transactions to assess their operational health and enable proactive manual human intervention before emerging problems escalate into widespread degradation or outages. See the PmScenarios? page for several specific examples.

Terminology

Service Provider - an implementation of the OSLC Performance Monitoring specification as a server. OSLC Performance Monitoring clients consume these services.

Performance Monitoring Resource - A resource managed by a Performance Monitoring service provider. The types of resources defined by this specification are FILL ME IN LATER.

Performance Monitoring Record - Defines the unit of information made available by a Performance Monitoring service provider.

Resource Definitions

The Performance Monitoring resource properties are not limited to the ones defined in this specification; service providers may provide additional properties. It is recommended that any additional properties exist in their own unique namespace and not use the namespaces defined in this specification.

A list of properties is defined for each type of resource. Most of these properties are identified in OSLC Core Appendix A: Common Properties. Any exceptions are noted. Relationship properties refer to other resources. These resources may be in any OSLC domain (including Performance Monitoring).

The diagram below shows the relationships between Performance Monitoring Resources. We need to draft resource definition(s) before more editing.

Diagram of OSLC Automation (sic) relationships

Resource: Performance Monitoring Record

  • Name: PerformanceMonitoringRecord
  • Description: A resource representing performance monitoring information.
  • Type URI http://open-services.net/ns/perfmon#PerformanceMonitoringRecord

PerformanceMonitoringRecord Properties

Prefixed Name Value-type Representation Range Description
OSLC Core: Common Properties
dcterms:contributor AnyResource Either any Contributor or contributors to resource (reference: Dublin Core). It is likely that the target resource will be an foaf:Person but that is not necessarily the case.
dcterms:created DateTime n/a n/a Timestamp of resource creation (reference: Dublin Core)
dcterms:creator AnyResource Either any Creator or creators of resource (reference: Dublin Core). It is likely that the target resource will be an foaf:Person but that is not necessarily the case.
dcterms:description XMLLiteral n/a n/a Descriptive text (reference: Dublin Core) about resource represented as rich text in XHTML content. SHOULD include only content that is valid and suitable inside an XHTML <div> element.
dcterms:identifier String n/a n/a A unique identifier for a resource. Assigned by the service provider when a resource is created. Not intended for end-user display.
dcterms:modified DateTime n/a n/a Timestamp of latest resource modification (reference: Dublin Core)
rdf:type Resource Reference n/a The resource type URIs.
dcterms:subject String n/a n/a Tag or keyword for a resource. Each occurrence of a dc:subject property denotes an additional tag for the resource.
dcterms:title XMLLiteral n/a n/a Title (reference: Dublin Core) of the resource represented as rich text in XHTML content.
oslc:instanceShape Resource Reference oslc:ResourceShape Resource Shape that provides hints as to resource property value-types and allowed values.
oslc:serviceProvider Resource Reference oslc:ServiceProvider The scope of a resource is a link to the resource's OSLC Service Provider.

Prefixed Name Value-type Representation Range Description
OSLC Performance Monitoring: Start of additional properties
oslc_perf:responseTime AnyResource Either oslc:Property Response time.

Appendix A: Samples (this section is informative)

See PmSpecificationV2Samples

Appendix C: Notices and References

Contributors

Reporting Issues

The working group participants who author and maintain this document monitor a distribution list where issues or questions can be raised, see Performance Monitoring Mailing List

Also the issues found with this specification and their resolution can be found at PmSpecificationV2Issues? .

Authors and Contact Information

Intellectual Property Covenant

The members of the Working Group (or as appropriate, their employers) have documented a Patent Non-Assertion Covenant and/or Patent License for implementations of Specifications based on this vocabulary, e.g. the Performance Monitoring 2.0 Specification, as described in the open-services.net Terms of Use.

References

Edit | Attach | Print version | History: r5 | r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r1 - 09 May 2012 - 14:12:54 - JohnArwe
 
This site is powered by the TWiki collaboration platform 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