Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Monitoring User Interface use cases"
| Line 18: | Line 18: | ||
==Use Case 1: Check the health of a resource== | ==Use Case 1: Check the health of a resource== | ||
| + | '''Actor:''' | ||
| + | |||
| + | System Admin | ||
| + | |||
| + | |||
| + | '''Description:''' | ||
| − | |||
In this use case, the user would run a canned report that looks at the health of a particular resource. The report should have some saved parameters that can applied, e.g. show me all the servers where CPU utilization if above 80%. The 80% should be customizable. | In this use case, the user would run a canned report that looks at the health of a particular resource. The report should have some saved parameters that can applied, e.g. show me all the servers where CPU utilization if above 80%. The 80% should be customizable. | ||
| − | |||
| + | '''Desired Outcome''' | ||
| + | |||
| + | The System Admin can quickly determine and evaluate the health of the system by studying a generated report. This information will help resolve issues such as service disruption and performance, and help determine what priority to place on the problem. | ||
| + | |||
| + | |||
| + | '''Assumptions''' | ||
| + | |||
| + | TBD | ||
| + | |||
| + | |||
| + | '''Process Flow''' | ||
| + | * Step 1 | ||
| + | * Step 2 | ||
==Use Case 2: Test/Debug resource instrumentation== | ==Use Case 2: Test/Debug resource instrumentation== | ||
| − | Description: | + | '''Actor:''' |
| + | |||
| + | Developer | ||
| + | |||
| + | |||
| + | '''Description:''' | ||
| − | + | TBD | |
==Use Case 3: ??== | ==Use Case 3: ??== | ||
Revision as of 10:33, 24 October 2006
Started some general brainstorming about the Monitor UI component of COSMOS. Started off with a general set of questions to help flush out the requirements.
Contents
General Requirements
- The Monitor UI is primarily a reporting user interface on top of the aggregated and normalized collected data for the purpose of health monitoring.
- What reports to provide?
- What templates should we provided
- “Auto update” on reports, e.g. refresh the view every “n” seconds/minutes?
- Support the idea of “drill down” reporting or only top level?
- What about linking/referencing external information from reports, e.g. to a run book? Could be an extension point of some sort?
- Simplified view for levels of sensitivity, e.g. a “sensitivity” filter. Response time may be an example where this would be appropriate.
- JDBC and/or XML data sources?
- What about login/security? JDBC connection only?
- Ad hoc reporting
Use Case 1: Check the health of a resource
Actor:
System Admin
Description:
In this use case, the user would run a canned report that looks at the health of a particular resource. The report should have some saved parameters that can applied, e.g. show me all the servers where CPU utilization if above 80%. The 80% should be customizable.
Desired Outcome
The System Admin can quickly determine and evaluate the health of the system by studying a generated report. This information will help resolve issues such as service disruption and performance, and help determine what priority to place on the problem.
Assumptions
TBD
Process Flow
- Step 1
- Step 2
Use Case 2: Test/Debug resource instrumentation
Actor:
Developer
Description:
TBD