Project%20Final%20Report

1
Project Final Report
System Monitoring Alarming Reporting Tracking
System (SMARTS)
Ron Bueler CS-701 3 May 2001
2
Overview

• Introduction
• Project summary
• Project evaluation
• Conclusion

3
Introduction

• Problem
• Monitor a set of hosts alarm on problems
• Store performance data
• Report on data collected
• Solution
• System Monitoring Alarming Reporting Tracking
  System (SMARTS)

4
Project Summary

• Design Goals
• Schedule
• Project Management
• Project Phases

5
Design Goals

• Flexibility
• Clonable components
• Standards based
• Non-proprietary solution
• Low system utilization
• Reliable data collection
• Heavily COTS based
• Role-based output

6
Schedule
7
Project Management

• Web Page
• Status
• Schedule
• Design
• Provides access to all project docs

8
Development Approach
9
Phases - Proposal/Initial Analysis

• Hardware/software environment
• Collect
• System CPU, disk space, and memory utilization
• Response time for each service
• Number of concurrent connections for each service
• Service availability times
• Application specific data for each service
• Alarm notification and escalation
• Automatic response triggers
• Comparison of similar systems

10
Phases - Requirements

• Narrative in nature
• High-level
• Alarm reporting
• Near real-time queries
• Standardized reports
• Management reports
• Non-functional
• Interfaces

11
Phases - Design
Collector Program
Step 1
Collector Output File
Collector Config File
Step 2
Transport Program
SMART Host
Oracle Tables
Step 3
Database Loader
Processed Tables
Step 4
Stored Procedures
Step 5
Email/Web File
Report Generation
12
Design Database Architecture
13
Phases Implementation

• CGI
• Build/configure
• Web server
• Perl Graphics Device (GD) module
• Perl DBI
• Development environment
• Perl 5.6
• Compaq Unix Tru64
• Oracle 8.1 RDBMS

14
Phases - Implementation
15
Phases - Implementation

• Web Based Reports
• Generated using Perl GD and PNG modules
• Email Based Reports
• Generated Daily and Monthly
• By Subscription Only

16
Phases - Test

• SMARTS reporting was rated MARGINAL

I inspection, D demo, A analysis, P pass,
F fail, NI not implemented H high priority,
M medium priority, L low priority
17
Project Evaluation

• Findings
• Challenges
• Usefulness
• Future

18
Project Evaluation - Findings

• Schedule estimation difficult
• Conduct more risk analysis
• Perform more analysis on COTS
• Good initial proposal/analysis
• Watch out for ripple effect of design mods
• Schedule flexibility paramount to success

19
Project Evaluation - Challenges

• Developer dependencies
• Synchronization of schedules
• Off-the-shelf component limitations
• Perl coding skills
• Installation configuration
• Oracle 8.1 DB server
• Netscape Enterprise Web Server
• Seagate Crystal Reports

20
Project Evaluation Usefullness

• Met basic requirements
• Solves most design goals
• Basic functions currently in use
• Strength of non-proprietary solutions

21
Project Evaluation Future

• Complete remaining requirements
• Deploy over more hosts
• Trend data store
• Implement userID/password protection
• Develop stored Oracle procedures to archive
  SMARTS data

22
Conclusion

• Introduction
• Project summary
• Project evaluation

Developed an alternative set of applications to
monitor a set of hosts using software systems
engineering practices and concepts learned during
my Graduate Program at UCCS.