System and method for analyzing network software application changes
First Claim
1. A method for network management comprising:
- loading, by a network management engine, a first component for execution;
linking, by the network management engine, the first component to a network wherein the first component is one of a plurality of components linked to the network;
modifying, by the network management engine, operating parameters of the first component;
tracking changes to a plurality of components in the network through the network management engine;
modifying tracking information for a second component by the network management engine, wherein the second component is one of the plurality of components;
implementing tracking modifications to the second component made by the network management engine on the network;
detecting a failing component based at least in part on the tracking changes;
in response to the detecting, the network management engine automatically;
performing an impact analysis to identify related components, wherein said related components are part of the plurality of components and, wherein said related components are associated with said failing component through the tracking information;
generating a problem ticket, wherein the problem ticket comprises tracking information related to the failing component, wherein the failing component is one of the plurality of components;
determining an owning group of the failing component based upon the tracking information;
routing the problem ticket to the owning group; and
tracking repair status information for repairing the failing component; and
automatically comparing the repair status information to a pre-established service level agreement specifying a level of service expected for repair of the failing component by the owning group.
5 Assignments
0 Petitions
Accused Products
Abstract
The present invention discloses systems and methods for monitoring, analyzing and reporting additions or changes to network software applications. The invention is achieved through a fully or partially automated system which allows for more accurate reporting and processing of metric data. The invention may link different subsystems that run a component so that any component change is automatically updated throughout the various subsystems. Further, the present invention allows users to view information related to component changes, thereby allowing the user to seek help related to that change. This information may include metrics, statistics, and/or other data associated with the components and component changes.
79 Citations
19 Claims
-
1. A method for network management comprising:
-
loading, by a network management engine, a first component for execution; linking, by the network management engine, the first component to a network wherein the first component is one of a plurality of components linked to the network; modifying, by the network management engine, operating parameters of the first component; tracking changes to a plurality of components in the network through the network management engine; modifying tracking information for a second component by the network management engine, wherein the second component is one of the plurality of components; implementing tracking modifications to the second component made by the network management engine on the network; detecting a failing component based at least in part on the tracking changes; in response to the detecting, the network management engine automatically; performing an impact analysis to identify related components, wherein said related components are part of the plurality of components and, wherein said related components are associated with said failing component through the tracking information; generating a problem ticket, wherein the problem ticket comprises tracking information related to the failing component, wherein the failing component is one of the plurality of components; determining an owning group of the failing component based upon the tracking information; routing the problem ticket to the owning group; and tracking repair status information for repairing the failing component; and automatically comparing the repair status information to a pre-established service level agreement specifying a level of service expected for repair of the failing component by the owning group. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. A computer-readable medium tangibly embodying a plurality of instructions, the plurality of instructions comprising:
-
instructions to load a first component for execution; instructions to link the first component to a network, wherein the first component is one of a plurality of components linked to the network; instructions to modify operating parameters of the first component; instructions to track changes to a plurality of components in the network through an network management engine; instructions to modify tracking information for a second component by the network management engine, wherein the second component is one of the plurality of components; instructions to implement tracking modifications to the second component made by the network management engine on the network; instruction to detect a failing component based at least in part on the tracking changes; instructions to respond to a detection of the failing component by automatically; performing an impact analysis to identify related components, wherein said related components are part of the plurality of components and, wherein said related components are associated with said failing component through the tracking information; generating a problem ticket, wherein the problem ticket comprises tracking information related to the failing component, wherein the failing component is one of the plurality of components; determining an owning group of the failing component based upon the tracking information; and routing the problem ticket to the owning group; and instructions to track repair status information for repairing the failing component; and instructions to automatically compare the repair status information to a pre-established service level agreement specifying a level of service expected for repair of the failing component by the owning group. - View Dependent Claims (15)
-
-
16. A network management system comprising:
-
a network interface communicating with a memory; the memory communicating with a processor; and the processor, when executing a computer program, is configured to; load a first component for execution; link the first component to a network, wherein the first component is one of a plurality of components linked to the network; modify operating parameters of the first component; track changes to a plurality of components in the network through an network management engine; modify tracking information for a second component, wherein the second component is one of the plurality of components; implement tracking modifications to the second component; detect a failing component based at least in part on the tracking changes; in response to the detecting, the network management system is configured to; perform an impact analysis to identify related components, wherein said related components are part of the plurality of components and, wherein said related components are associated with said failing component through the tracking information; generate a problem ticket, wherein the problem ticket comprises tracking information related to the failing component, wherein the failing component is one of the plurality of components; determine an owning group of the failing component based upon the tracking information; and route the problem ticket to the owning group; and track repair status information for repairing the failing component; and automatically compare the repair status information to a pre-established service level agreement specifying a level of service expected for repair of the failing component by the owning group. - View Dependent Claims (17, 18, 19)
-
Specification