Assessing operational impact in enterprise systems with dependency discovery and usage mining
A framework for monitoring the dependencies between users, applications, and other system components, combined with the actual access times and frequencies, was proposed. Operating system commands were used to extract event information from the end-user workstations about the dependencies between sy...
Main Author: | |
---|---|
Published: |
Georgia Institute of Technology
2010
|
Subjects: | |
Online Access: | http://hdl.handle.net/1853/31795 |
id |
ndltd-GATECH-oai-smartech.gatech.edu-1853-31795 |
---|---|
record_format |
oai_dc |
spelling |
ndltd-GATECH-oai-smartech.gatech.edu-1853-317952013-01-07T20:35:09ZAssessing operational impact in enterprise systems with dependency discovery and usage miningMoss, Mark BomiImpact analysisEnterprise application integration (Computer systems)Management information systemsComputer system failuresCommunication of technical informationA framework for monitoring the dependencies between users, applications, and other system components, combined with the actual access times and frequencies, was proposed. Operating system commands were used to extract event information from the end-user workstations about the dependencies between system, application and infrastructure components. Access times of system components were recorded, and data mining tools were leveraged to detect usage patterns. This information was integrated and used to predict whether or not the failure of a component would cause an operational impact during certain time periods. The framework was designed to minimize installation and management overhead, to consume minimal system resources (e.g. network bandwidth), and to be deployable on a variety of enterprise systems, including those with low-bandwidth and partial-connectivity characteristics. The framework was implemented in a test environment to demonstrate the feasibility of this approach. The system was tested on small-scale (6 computers in the GT CERCS Laboratory over 35 days) and large-scale (76 CPR nodes across the entire GT campus over 4 months) data sets. The average size of the impact topology was shown to be approximately 4% of the complete topology, and this size reduction was related to providing system administrators the capability to better identify those users and resources most likely to be affected by a designated set of component failures during a designated time period.Georgia Institute of Technology2010-01-29T19:53:44Z2010-01-29T19:53:44Z2009-07-15Dissertationhttp://hdl.handle.net/1853/31795 |
collection |
NDLTD |
sources |
NDLTD |
topic |
Impact analysis Enterprise application integration (Computer systems) Management information systems Computer system failures Communication of technical information |
spellingShingle |
Impact analysis Enterprise application integration (Computer systems) Management information systems Computer system failures Communication of technical information Moss, Mark Bomi Assessing operational impact in enterprise systems with dependency discovery and usage mining |
description |
A framework for monitoring the dependencies between users, applications, and other system components, combined with the actual access times and frequencies, was proposed. Operating system commands were used to extract event information from the end-user workstations about the dependencies between system, application and infrastructure components. Access times of system components were recorded, and data mining tools were leveraged to detect usage patterns. This information was integrated and used to predict whether or not the failure of a component would cause an operational impact during certain time periods. The framework was designed to minimize installation and management overhead, to consume minimal system resources (e.g. network bandwidth), and to be deployable on a variety of enterprise systems, including those with low-bandwidth and partial-connectivity characteristics. The framework was implemented in a test environment to demonstrate the feasibility of this approach. The system was tested on small-scale (6 computers in the GT CERCS Laboratory over 35 days) and large-scale (76 CPR nodes across the entire GT campus over 4 months) data sets. The average size of the impact topology was shown to be approximately 4% of the complete topology, and this size reduction was related to providing system administrators the capability to better identify those users and resources most likely to be affected by a designated set of component failures during a designated time period. |
author |
Moss, Mark Bomi |
author_facet |
Moss, Mark Bomi |
author_sort |
Moss, Mark Bomi |
title |
Assessing operational impact in enterprise systems with dependency discovery and usage mining |
title_short |
Assessing operational impact in enterprise systems with dependency discovery and usage mining |
title_full |
Assessing operational impact in enterprise systems with dependency discovery and usage mining |
title_fullStr |
Assessing operational impact in enterprise systems with dependency discovery and usage mining |
title_full_unstemmed |
Assessing operational impact in enterprise systems with dependency discovery and usage mining |
title_sort |
assessing operational impact in enterprise systems with dependency discovery and usage mining |
publisher |
Georgia Institute of Technology |
publishDate |
2010 |
url |
http://hdl.handle.net/1853/31795 |
work_keys_str_mv |
AT mossmarkbomi assessingoperationalimpactinenterprisesystemswithdependencydiscoveryandusagemining |
_version_ |
1716475232711081984 |