Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "COSMOS Design 214143"

(New page: Back to Data Reporting Design = '''Change History''' = {|{{BMTableStyle}} !align="left"|Name: !align="left"|Date: !align="left"|Revised Sections: |- |Sheldo...)
 
(''' Workload Estimation''')
Line 26: Line 26:
 
|-
 
|-
 
| align="left" | Code
 
| align="left" | Code
| 2
+
|  
 
|
 
|
 
|-
 
|-
 
| align="left" | Test
 
| align="left" | Test
| 0.5
+
|  
 
|
 
|
 
|-
 
|-
 
| align="left" | Documentation
 
| align="left" | Documentation
| 0.5
+
|  
 
|
 
|
 
|-
 
|-
 
| align="left" | Build and infrastructure
 
| align="left" | Build and infrastructure
| 0.2
+
|  
 
|
 
|
 
|-
 
|-
Line 46: Line 46:
 
|-
 
|-
 
! align="right" | TOTAL
 
! align="right" | TOTAL
| 3.4
+
|  
 
|
 
|
 
|}
 
|}

Revision as of 02:39, 8 January 2008

Back to Data Reporting Design

Change History

Name: Date: Revised Sections:
Sheldon Lee-Loy 01/07/2008
  • Initial version

Workload Estimation

Rough workload estimate in person weeks
Process Sizing Names of people doing the work
Design 0.2 Sheldon Lee-Loy
Code
Test
Documentation
Build and infrastructure
Code review, etc.*
TOTAL

'* - includes other committer work (e.g. check-in, contribution tracking)

Purpose

Currently the navigation widget in the COMOSUI provides a mechanism to submit CMDBf queries to MDRs. These queries are constructed by the end user and are not persisted. As a result the queries are lost once the COSMOS UI application shutsdown.

Requirement

This enhancement proposes a mechanism for developers to register predefined cmdbf queries with the data visualization user interface.


The following illustrates a query that is useful against a statistical MDR: I want the memory usage data for the machine that is running the tomcat 59223 server?

A CMDBf query file would be created to capture the above query. A registry is needed to associate this query with a specific MDR that contains the information.

The following illustrates how the navigation tree will present predefined queries.

+MDR (Asset Repository) +MDR (Monitoring Repository) +MDR (Statistical Repository)

   + Tomcat Server 5912334
          + All Statistical data from 12/2/2003 to 12/2/2004
          + All Statistical data from 12/2/2004 to 12/2/2005
          + All Statistical data from 12/2/2005 to 12/2/2006
          + Memory Usage
   + Websphere Server 55224
          + All Statistical data from 12/2/2003 to 12/2/2004
          + All Statistical data from 12/2/2004 to 12/2/2005
          + All Statistical data from 12/2/2005 to 12/2/2006


Note the above shows a "query tree". The "MDR (Statistical Repository)" contains two top level queries that will query for statistical data based on the server id. In contrast, each of these queries contain nested queries that filter the queries further by date. Note that this query tree defines away to organize the queries for a particular mdr. Developers would create the corresponding cmdf query files to construct this query tree. A registration mechanism is required in the data visualization component to recognize these cmdbf file and present this queries in the navigator view.

Meta data information should be associated with a query file that describes the query. Tagging this file would also be useful. The meta data file should also contain management rules that will match the data manager that this query should apply to.

Design

Back to the top