US20010052087A1 - Method and apparatus for monitoring a network environment - Google Patents
Method and apparatus for monitoring a network environment Download PDFInfo
- Publication number
- US20010052087A1 US20010052087A1 US09/067,319 US6731998D US2001052087A1 US 20010052087 A1 US20010052087 A1 US 20010052087A1 US 6731998 D US6731998 D US 6731998D US 2001052087 A1 US2001052087 A1 US 2001052087A1
- Authority
- US
- United States
- Prior art keywords
- network
- data
- alarm
- cognitive
- network environment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 24
- 238000000034 method Methods 0.000 title claims description 84
- 230000001149 cognitive effect Effects 0.000 claims abstract description 165
- 238000004458 analytical method Methods 0.000 claims abstract description 51
- 230000003213 activating effect Effects 0.000 claims abstract description 5
- 238000013480 data collection Methods 0.000 claims description 17
- 230000009471 action Effects 0.000 description 28
- 238000004891 communication Methods 0.000 description 26
- 230000004044 response Effects 0.000 description 21
- 230000009467 reduction Effects 0.000 description 13
- 238000010586 diagram Methods 0.000 description 10
- 230000007246 mechanism Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 6
- 230000002596 correlated effect Effects 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000001788 irregular Effects 0.000 description 4
- 230000000694 effects Effects 0.000 description 3
- 230000003068 static effect Effects 0.000 description 3
- 230000001960 triggered effect Effects 0.000 description 3
- 230000008859 change Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012935 Averaging Methods 0.000 description 1
- 230000004913 activation Effects 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
- H04L41/5003—Managing SLA; Interaction between SLA and QoS
- H04L41/5009—Determining service level performance parameters or violations of service level contracts, e.g. violations of agreed response time or mean time between failures [MTBF]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0876—Network utilisation, e.g. volume of load or congestion level
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0681—Configuration of triggering conditions
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/04—Processing captured monitoring data, e.g. for logfile generation
- H04L43/045—Processing captured monitoring data, e.g. for logfile generation for graphical visualisation of monitoring data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
- H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
- H04L43/103—Active monitoring, e.g. heartbeat, ping or trace-route with adaptive polling, i.e. dynamically adapting the polling rate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/16—Threshold monitoring
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W24/00—Supervisory, monitoring or testing arrangements
- H04W24/08—Testing, supervising or monitoring using real traffic
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Environmental & Geological Engineering (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- The present invention relates to network monitoring systems. More specifically, the invention provides a system that detects problems or potential problems in a network environment.
- Networks are used to interconnect multiple devices, such as computing devices, and allow the communication of information between the various interconnected devices. Many organizations rely on networks to communicate information between different individuals, departments, work groups, and geographic locations. In many organizations, a network is an important resource that must operate efficiently. For example, networks are used to communicate electronic mail (e-mail), share information between individuals, and provide access to shared resources, such as printers, servers, and databases. A network failure or inefficient operation may significantly affect the ability of certain individuals or groups to perform their required functions.
- A typical network contains multiple interconnected devices, including computers, servers, printers, and various other network communication devices such as routers, bridges, switches, and hubs. The multiple devices in a network are interconnected with multiple communication links that allow the various network devices to communicate with one another. If a particular network device or network communication link fails, multiple devices, or the entire network, may be affected.
- Network management is the process of managing the various network devices and network communication links to provide the necessary network services to the users of the network. Typical network management systems collect information regarding the operation and performance of the network and analyze the collected information to detect problems in the network. For example, a high network utilization or a high network response time may indicate that the network (or a particular device or link in the network) is approaching an overloaded condition. In an overloaded condition, network devices may be unable to communicate at a reasonable speed, thereby reducing the usefulness of the network. In this situation, it is important to identify the network problem and the source of the problem such that the proper network operation can be restored.
- Typically, existing network management systems compare the current network performance parameters to one or more threshold values associated with the parameters. For example, an upper threshold of 90 percent may be associated with a network utilization parameter, such that an alarm is generated if the network utilization exceeds 90 percent. A network utilization in excess of 90 percent may indicate an approaching overload condition. Similar thresholds may be provided for other network parameters such as response time or number of errors. Generally, only an upper threshold is provided (e.g., network utilization above a particular threshold).
- Typically, thresholds used by existing systems are absolute such that an alarm is generated each time a threshold is crossed. For example, if a network utilization parameter has an associated upper threshold of 90 percent, an alarm is generated if the network utilization is 91 percent for a specified period of time. However, an alarm is not generated if the network utilization is 90 percent for a long period of time. Also, if network utilization drops to five percent because a periodic backup process was not activated, an alarm is not generated since the threshold associated with network utilization was not exceeded.
- These existing systems that use thresholds to identify network problems determine the threshold values (e.g., upper limits) based on how the network administrator believes the network should operate. Since these thresholds are typically static, they do not change automatically with changes in the network operation or network configuration. Instead, the network administrator must recalculate (or re-estimate) threshold values manually when a network change occurs. Typically, a single set of threshold values are used for all time periods. Thus, the same thresholds may be used during periods of heavy network utilization (e.g., 2:00 p.m. on a business day) and during periods of minimal network utilization (e.g., 10:00 p.m. on a holiday). Thus, the same threshold values are applied at all times, regardless of the expected or historical network utilization.
- For example, if a significant increase in network utilization occurs every Monday at 9:00 a.m. (i.e., the upper threshold is crossed), an alarm may be generated every Monday even though this is a common event that does not necessarily indicate a network problem. Similarly, if a significant increase in network utilization occurs (without crossing the upper threshold) at a time when the network utilization is typically minimal, an alarm is not generated even though a network problem may exist. Thus, existing systems do not consider typical or historical network operation when determining whether a network problem exists.
- It is therefore desirable to provide a network-related monitoring system that detects problems or potential problems in a network environment by comparing recent network operation with historical network operation.
- Embodiments of the present invention provide a network-related monitoring system that detects problems or potential problems in a network environment by comparing current network operation and performance data to historical network operation and performance data. The present invention is capable of monitoring the operation and performance of a network environment, including various network devices. In addition to monitoring an overall network environment, embodiments of the present invention monitor the operation and performance of specific devices (such as network devices), including various components or sub-systems within a device. Embodiments of the invention also monitor applications running on one or more devices or systems in a network environment.
- An embodiment of the invention provides a system that monitors a network environment by collecting recent data associated with operation of the network environment. The network environment is analyzed by comparing the collected data with historical data associated with the operation of the network environment. Problems are identified based on the analysis of the network environment.
- In a particular embodiment of the invention, the historical data is represented in multiple cognitive signatures.
- Another embodiment of the invention updates the historical data to include the collected data.
- Embodiments of the invention generate an alarm if a problem is identified.
- An embodiment of the invention monitors a network device by collecting recent data associated with operation of the network device. The network device is analyzed by comparing the collected data with historical data associated with the operation of the network device. Problems are identified based on the analysis of the network device.
- Other embodiments of the invention collect data associated with the performance of a component or sub-system within a network device.
- The present invention is illustrated by way of example in the following drawings in which like references indicate similar elements. The following drawings disclose various embodiments of the present invention for purposes of illustration only and are not intended to limit the scope of the invention.
- FIG. 1 illustrates an embodiment of a network environment in which the present invention can be implemented.
- FIG. 2 illustrates an embodiment of a network monitor capable of detecting problems or potential problems in a network environment.
- FIG. 3 is a flow diagram illustrating an embodiment of a procedure for detecting problems or potential problems in a network environment.
- FIG. 4 is a flow diagram illustrating an embodiment of a procedure for reducing data collected from a network.
- FIG. 5 illustrates an embodiment of a cognitive signature module.
- FIG. 6A illustrates an exemplary cognitive signature in a graphical manner.
- FIG. 6B is a flow diagram illustrating an embodiment of a procedure for generating and modifying cognitive signatures.
- FIG. 7 illustrates an embodiment of an analysis module.
- FIG. 8 is a flow diagram illustrating an embodiment of a procedure for analyzing performance or operation of a network environment.
- FIG. 9 illustrates an embodiment of an alarm generator.
- FIG. 10 is a flow diagram illustrating an embodiment of a procedure for generating an alarm based on analysis of network performance.
- FIG. 11 illustrates an embodiment of a computer system that can be used with the present invention.
- The following detailed description sets forth numerous specific details to provide a thorough understanding of the invention. However, those of ordinary skill in the art will appreciate that the invention may be practiced without these specific details. In other instances, well-known methods, procedures, protocols, components, and circuits have not been described in detail so as not to obscure the invention.
- The present invention is related to a network-related monitoring system that detects problems or potential problems in a network environment by comparing current network operation and performance data to historical network operation and performance data. The monitoring system can be used to monitor the operation and performance of a network environment, including various network devices. As discussed herein, network environment shall include all systems, components, sub-systems, network devices, communication links, applications, and any other systems or components (including both software and hardware) coupled to or used in conjunction with a network.
- In addition to monitoring an overall network environment, the monitoring system is able to monitor the operation and performance of specific devices (such as network devices), including various components or sub-systems within a device. For example, embodiments of the invention are capable of monitoring the performance of a central processing unit (CPU), available memory, and other device conditions. The invention can also monitor applications running on one or more devices or systems (e.g., monitoring application response time).
- The historical operation and performance data is updated regularly to reflect recent data collected regarding recent performance of the network and/or devices being monitored. Additionally, embodiments of the present invention consider threshold values (both upper threshold limits and lower threshold limits) when determining whether a problem (or potential problem) exists in a particular network environment. Thus, the monitoring system uses both thresholds and dynamic historical data to detect problems or potential problems in a network environment.
- FIG. 1 illustrates an embodiment of a network environment in which the present invention can be implemented. The network environment of FIG. 1 contains multiple network devices coupled to one another using a pair of
networks workstations 14 and a pair ofservers 16 are coupled tonetwork 10. Additionally, aprinter 18 and anetwork monitor 22 are coupled tonetwork 10. A network device 20 (such as a router, bridge, switch or gateway) is coupled to bothnetwork 10 andnetwork 12.Network device 20 allows network data to be exchanged betweennetwork 10 andnetwork 12, thereby allowing network devices coupled tonetwork 10 to communicate with other network devices coupled tonetwork 12. Another pair ofworkstations 14 and aserver 16 are also coupled tonetwork 12. Although FIG. 1 shows four workstations and three servers, a particular network environment may contain any number of workstations, servers, printers, or other network devices interconnected with one another in any configuration.Networks network 10 andnetwork 12 may use different protocols and different network topologies. If different protocols or different topologies are used, then networkdevice 20 is required to translate or otherwise convert data between the two different protocols or two different topologies. - Network monitor22 is coupled to
network 10, but is capable of monitoring network devices, interfaces, and communication links associated withnetwork 10 as well asnetwork 12. Network monitor 22 is also able to monitor the operation and performance of various sub-systems, components, or applications contained within a network device. For example, network monitor 22 can monitor the CPU performance, memory utilization, and application response time of workstations and servers contained in the network environment. Although asingle network monitor 22 is shown in FIG. 1, in an alternate embodiment of the invention, a separate network monitor is coupled tonetwork 12. In this embodiment, network monitor 22 monitors network devices, interfaces, and communication links associated withnetwork 10, while the network monitor coupled tonetwork 12 monitors network devices, interfaces, and communication links associated withnetwork 12. In other embodiments of the invention, asingle network monitor 22 is capable of monitoring network devices, interfaces, and communication links associated with three or more different networks. - FIG. 1 illustrates an exemplary network environment. Those of ordinary skill in the art will appreciate that the teachings of the present invention can be used with any number of network environments and network configurations. Furthermore, the teachings of the present invention can be used to monitor any network device, system, component, or application for which information can be gathered, either directly or indirectly. Additionally, the present invention is capable of monitoring any communication link or interface within a network or between a network and a network device. Although FIG. 1 illustrates network monitor22 as a separate network device, network monitor 22 may be incorporated into another network device, such as
server 16. - FIG. 2 illustrates an embodiment of a
network monitor 22 capable of detecting problems or potential problems in a network environment. Network monitor 22 includes adata collection module 30 that collects information from various devices or applications, such as information regarding network utilization (or device utilization), lost packets, response time, or number of errors.Data collection module 30 collects information regarding the operation or performance of the network environment on one or more communication links 31.Data collection module 30 can collect data from any number of networks and any number of network devices or applications.Data collection module 30 is coupled to adata reduction module 32, which reduces the collected data by reducing the granularity of the data over time and performing statistical reduction of the data, as discussed below. -
Data reduction module 32 is coupled to acognitive signature module 34 and astorage device 36.Cognitive signature module 34 generates and maintains multiple dynamic cognitive signatures based on the data collected from the network. A cognitive signature represents the normal operating mode for a particular network device, network interface, system, application, or communication link with which the cognitive signature is associated. The cognitive signature is based on actual historical data collected regarding the operation and performance of the network environment. The cognitive signature is dynamic, such that it is continually updated to include the most recent data collected by the data collection module. - In a particular embodiment of the invention, a separate cognitive signature is provided for each day of the week. A cognitive signature for a particular day of the week may include data separated into multiple time periods (e.g., each hour of the day). For example, a cognitive signature for Tuesday may include a particular time period that represents the normal operating mode (based on collected historical data) for a particular network device from 9:00 a.m. to 10:00 a.m. on Tuesday. A cognitive signature for Saturday may include a time period that represents the normal operating mode for a particular network interface from 2:00 p.m. to 3:00 p.m. on Saturday. Additional details regarding cognitive signatures are discussed below.
- In the embodiment of FIG. 2,
cognitive signature module 34 receives data fromdata reduction module 32. In this embodiment, the granularity of the collected data has already been reduced when received bycognitive signature module 34. In an alternate embodiment of the invention,cognitive signature module 34 may receive data directly fromdata collection module 30. In this alternate embodiment,cognitive signature module 34 receives the actual data collected, rather than a reduced set of data. Thus, the cognitive signatures can be generated using the actual data without any loss of detail due to averaging or other data reduction procedures. -
Storage device 36 may be any type of mechanism capable of storing data, such as a random access memory (RAM), disk drive, or tape drive.Storage device 36 is capable of receiving data fromdata reduction module 32,cognitive signature module 34, and ananalysis module 38.Analysis module 38 receives collected data fromdata collection module 30, and receives one or more cognitive signatures fromcognitive signature module 34.Analysis module 38 analyzes current performance or operation of the network environment by comparing the data collected via the network with the cognitive signatures, which represent past performance or operation of the network environment at similar times for similar devices, systems, or applications.Analysis module 38 may also compare the current data collected with one or more threshold values.Analysis module 38 is coupled to analarm generator 40. Based on the results of the analysis performed byanalysis module 38, an alarm signal may be communicated to alarmgenerator 40. In response to the alarm signal,alarm generator 40 may generate an e-mail message to a network administrator or other personnel, initiate a page to a network administrator's pager, or communicate the alarm information to another system or application. Additionally,alarm generator 40 may initiate a pre-programmed procedure that is executed in response to a particular type of alarm. - FIG. 3 is a flow diagram illustrating an embodiment of a procedure for detecting problems or potential problems in a network environment. At
step 42, data is collected from the network. As discussed above, the collected data may include various network performance and operation data such as network utilization and application response times. The data is collected, for example, usingdata collection module 30 shown in FIG. 2. A request for information (such as a status request) is sent to one or more network devices or applications at various time intervals. The request for information requests details regarding particular operation or performance parameters that are available from the network device or application. For example, the request for information may request the current utilization of each interface or network port on a particular network device or may determine the current response time for a particular application. Additionally, the request for information may request details regarding the number of errors or discarded packets associated with each interface or port on a network device. Information can be collected from the various network devices and applications at regular time intervals, such as every five minutes. - The data collection module maintains a table or other collection of information to identify the various network devices and applications from which data is collected. For each network device, the table identifies the parameters or performance data to be requested and the time interval between requests. Thus, the data collected from the network can be selective with respect to the network devices, applications, interfaces or communication ports within a particular device, and with respect to polling time intervals.
- At
step 44, the procedure reduces the data collected from the network instep 42. Additional details regarding the reduction of the collected data is provided below with respect to FIG. 4.Step 46 analyzes operation and performance by comparing the current data collected from the network (i.e., the data representing the current performance or operation of the network environment) with the cognitive signatures ( i.e., the historical data regarding performance or operation of the network environment). Additional details regarding this analysis are provided below. - At
step 48, the procedure determines whether a problem or a potential problem has been detected based on the analysis performed instep 46. If a problem or a potential problem is not detected, then the procedure branches to step 50 to generate and/or modify the cognitive signatures based on data collected from the network and previous problem history. The cognitive signatures are generated (e.g., during an initialization period) or modified to include the recent data collected. This regular update of the cognitive signatures allows the cognitive signatures to be adjusted in response to changes in the operation and performance of the network environment. - If a problem or a potential problem is detected in
step 48, the procedure continues to step 52, where an alarm is generated indicating the problem or the potential problem detected.Step 52 also generates a problem history. A problem history is maintained for each problem identified. The problem history identifies information about the source and cause of the problem (if known) as well as the duration of the problem. The problem history may also include the number of occurrences of the problem and may identify other problems that occurred at similar times, thereby allowing the correlation of multiple problems. - Although an alarm is generated in52, the alarm may not be communicated to the network administrator, depending on the severity of the alarm. Further, if a potential problem is detected, the alarm may not be communicated to the network administrator depending on whether the potential problem is validated as an actual problem. An alarm generator (e.g.,
alarm generator 40 in FIG. 2) may determine whether to notify the network administrator and determine the manner in which the administrator is notified (e.g., by e-mail, pager, or other mechanism). -
Step 54 of FIG. 3 generates or modifies the cognitive signatures based on data collected from the network. As mentioned above, the cognitive signatures are dynamic and continually updated as new data is collected from the network. However, in certain situations, the cognitive signatures may not be updated. For example, if the collected data is significantly different than the associated cognitive signature (e.g., indicating a significant problem), then the cognitive signature may not be updated. Updating the cognitive signature in this atypical situation may skew the cognitive signature. In another example, if the collected data is slightly different than the associated cognitive signature (e.g., indicating a potential minor problem), then the cognitive signature may be update but the weighting provided to the current data is reduced, thereby reducing the current data's affect on the cognitive signature. - FIG. 4 is a flow diagram illustrating an embodiment of a procedure for reducing data collected from a network. At
step 60, data is collected from one or more network devices or applications in a network. Atstep 62, the procedure determines an average value, a peak value, and a minimum value for each of type of current data collected from the network. - At
step 64, the procedure stores the data collected from the network during the past period in five minute samples. Atstep 66, the procedure identifies data collected from the network during the past four weeks (but not the past 24 hours) and reduces the granularity of the data to one hour samples. Thus, rather than storing twelve values each hour (five minute samples), the twelve values are consolidated into a single value representing the entire hour. This reduction in data granularity significantly reduces the storage space required for this older data. Thus, the twelve average values for each parameter are consolidated into a single average value. Similarly, the twelve peak values and the twelve minimum values are consolidated into a single peak value and a single minimum value, respectively. -
Step 68 identifies data collected from the network during the past three months (but not the past four weeks) and reduces the granularity of the data to four hour samples. This further reduction in data granularity further reduces the storage space required to maintain the historical data.Step 70 identifies data collected from the network more than three months ago and reduces the granularity of the data to one day samples. Thus, the data granularity is reduced as the age of the data increases. The manner in which data is reduced may vary from one device to another or from one interface to another. FIG. 4 illustrates one data reduction procedure that can be used with the present invention. Those of ordinary skill in the art will appreciate that numerous other data reduction procedures may be utilized with the present invention. Furthermore, in alternate embodiments of the invention, data reduction procedures are not used. Although these alternate embodiments require additional storage space for the collected data, they provide increased data granularity (i.e., increased detail). - FIG. 5 illustrates an embodiment of a cognitive signature module (e.g.,
module 34 shown in FIG. 2).Cognitive signature module 34 includes acognitive signature generator 80 that creates and modifies multiple cognitive signatures. As discussed above, a separate cognitive signature is typically used for each device, application or interface in a network environment. Additionally, separate cognitive signature values can be maintained for different time periods on different days of the week.Cognitive signature generator 80 receives various information regarding network operation, includingcognitive signatures 82 andexception information 86. This information is received bycognitive signature generator 80 ondata path 84.Cognitive signatures 82 represent the operation and performance of the network environment based on data collected during previous weeks.Cognitive signatures 82 are received from, for example,data collection module 30 or data reduction module 32 (FIG. 2). -
Cognitive signatures 82 are adjusted, as necessary, to ignore data during time periods when the network is down or when significant components of the network (e.g., a router or a server) are down or offline. For example, if several network servers are down for maintenance from 4:00 p.m. to 5:00 p.m. on a particular Friday, the portion of the cognitive signature associated with that time period on Friday is not adjusted. When several network servers are down, data collected from the network is likely to be significantly different from the data that would be collected if the servers were operating. For example, response time may increase significantly when a network device is down or malfunctioning. Updating the cognitive signature in this situation would incorrectly skew the cognitive signatures. Thus, rather than incorporating this atypical information into the cognitive signatures, one or more network parameters are ignored during the time period during which the network servers are down. Therefore, the cognitive signatures associated with these network parameters is not changed. -
Exception information 86 contains network operation and performance data regarding infrequent events and events that do not follow a regular pattern. For example, if an increase in network utilization occurs every Monday from 9:00 a.m.-10:00 a.m., the information is included in a cognitive signature because the event occurs on a regular basis. However, other events may occur on an irregular basis. For example, a significant increase in network utilization may occur on the last business day of each month. Similarly, a significant decrease in network utilization may occur on holidays. These irregular but schedulable events are not incorporated into thecognitive signatures 82 and, instead, are stored asseparate exception information 86.Cognitive signature generator 80 creates and maintains separate cognitive signatures for each event that occurs on an irregular but schedulable basis. Thus, when selecting an appropriate cognitive signature for use in analyzing current network operation and performance,cognitive signature generator 80 considers bothcognitive signatures 82 andexception information 86. -
Cognitive signature generator 80 also produces signature correlation factors 88, which indicate the degree of correlation associated with each cognitive signature. The signature correlation factors indicate, based on historical data, the likelihood that a particular network parameter will fall within the range of values defined by the cognitive signature. Certain performance data may be relatively constant from one week to the next during a particular time period. For example, network utilization between 3:00 a.m. and 4:00 a.m. on Saturday may be between five percent and ten percent with very infrequent deviations. In this example, the signature correlation factor may be 0.9, indicating that there is a 90 percent likelihood that the collected data associated with the cognitive signature will be within the range of values specified by the cognitive signature. - In another situation, a particular cognitive signature may not be highly correlated, indicating that the collected data varies significantly. For example, network utilization between 9:00 a.m. and 10:00 a.m. on Monday may vary between 20 percent and 80 percent. In this situation, the correlation factor may be 0.2.
- Signature correlation factors are used when analyzing collected data and determining whether to activate an alarm. Additionally, the signature correlation factors are used to determine the severity of an alarm. For example, if the current data collected is outside the cognitive signature by ten percent and the cognitive signature is highly correlated, then the situation is considered an unusual event, and may cause the generation of an alarm. If the current data collected is outside the cognitive signature by 50 percent, then the situation is considered a serious event. However, if the cognitive signature is not highly correlated, then data that is ten percent outside the cognitive signature is not considered to be an important event and does not trigger an alarm. When the cognitive signature is not highly correlated, the current data may need to be outside the cognitive signature by 75 percent or more before an alarm is generated. Additional details regarding the analysis of collected data, including the use of signature correlation factors, are discussed below.
- Various
cognitive signature tools 90 are available for use bycognitive signature generator 80.Cognitive signature tools 90 can be used to update exception information, such as identifying upcoming holidays or scheduled down times for servers or other devices in the network environment.Cognitive signature tools 90 can also modify cognitive signatures to “undo” the effects of data collected during a particular time period. For example, if a network failure occurred during a particular time period and performance data for that time period was integrated into the cognitive signatures, a tool can be activated to remove the effects of this data from the cognitive signature. This tool thereby eliminates any skewing of the cognitive signature due to the network failure. - FIG. 6A illustrates an exemplary
cognitive signature 91 in a graphical manner. Embodiments of the invention store the cognitive signature values in a table or other data structure that is easily accessed by a processing device. Cognitive signatures are not necessarily stored in a graphical manner. FIG. 6A illustratescognitive signature 91 graphically for purposes of explanation.Cognitive signature 91 includes three components: anaverage line 91 a, a peak line 91 b, and a minimum line 91 c. The peak and minimum lines 91 b and 91 c define a band or range of values that generally define “typical” values for the parameter associated withcognitive signature 91.Cognitive signature 91 is associated with a particular day of the week (e.g., Tuesday) and a particular network parameter (e.g., network utilization). - Referring to FIG. 6A, the horizontal axis represents time-of-day and the vertical axis represents the utilization of the network (measured from zero percent to 100 percent).
Cognitive signature 91 shows that network utilization is generally highest around 4:00 a.m. and 11:00 a.m. Thus, a high network utilization at 11:15 a.m. on a Tuesday might not represent a problem since the utilization parameter is within cognitive signature 91 (i.e., between the peak line 91 b and the minimum line 91 c). However, a high network utilization at 4:30 p.m. on Tuesday represents a problem (or a potential problem) becausecognitive signature 91 indicates that, historically, network utilization has not been high at that time. Similarly, a low network utilization at 4:00 a.m. on Tuesday may indicate a problem becausecognitive signature 91 indicates that the network utilization has historically been high at that time. Therefore,cognitive signature 91 is used to identify problems when the associated parameter exceeds peak line 91 b or falls below minimum line 91 c. - As discussed above, data is collected from the network at various intervals (e.g., every five minutes).
Cognitive signature 91 may contain all of the data collected from the network (e.g., five minute samples) or may be reduced to less frequent intervals (e.g., one hour samples). If using one hour samples,cognitive signature 91 will include three values (average, peak, and minimum) for each interval. Thus, all data collected during the one hour period is represented by three values. It will be appreciated that time intervals of any size can be used to generate a cognitive signature. As discussed above, in a particular embodiment of the invention, a separate cognitive signature is maintained for each day of the week in combination with each monitored parameter. Thus, separate cognitive signatures are provided for network utilization on Tuesday, network utilization on Wednesday, application response time on Tuesday, application response time on Wednesday, and so forth. A network monitoring system can maintain hundreds or thousands of cognitive signatures, depending on the number of network environment parameters being monitored. - FIG. 6B is a flow diagram illustrating an embodiment of a procedure for generating and modifying cognitive signatures. When a network monitor first begins monitoring a network environment, or begins monitoring a new network device, no cognitive signature exists with which the current collected data can be compared. Thus, in
step 92 of FIG. 6B, an initialization process is performed to initialize the cognitive signatures and the cognitive signature correlation factors.Step 92 also collects information regarding the network environment, including information regarding various network devices, systems, and applications. During the initialization period, cognitive signatures are generated using the collected data. Since no historical data is available for the same period in previous weeks, the current data may be compared to the cognitive signature data associated with the previous hour or the previous day. After the initialization process has collected data for seven days, cognitive signatures will be available for all time periods on each day of the week. At this point, current data collected from the network is compared to the appropriate cognitive signatures. - At
step 94, the procedure collects data (e.g., performance data) from the network. This collected data is referred to as the current data. Atstep 96, the procedure identifies exception information and determines whether the current data is within an exception period. Exception periods include holidays, maintenance periods, scheduled down times for one or more network devices, and similar irregular events. The exception information can be stored in a table or other data structure and includes the start time and end time of the exception period. The exception information also includes the action to be taken during the exception information. For example, the action may be to ignore all data collected during the exception period (i.e., do not generate alarms or update cognitive signatures) or apply a different weighting to the collected data when updating the cognitive signatures. Different action may be taken depending on the parameter being monitored or the network device or application providing the data. For example, a scheduled down time for a particular device may cause data associated with that device to be ignored, while data associated with other devices is handled in the normal manner. - If the current data is within an exception period, then the procedure branches from
step 98 to step 100 to take the appropriate action associated with the exception period. If the current data is not within an exception period, then the procedure continues fromstep 98 to step 102 to update the cognitive signature based on the existing cognitive signature and the current data. In a particular embodiment of the invention, the cognitive signature value(s) for the period associated with the current data is updated according to the following formula. - New Cog.Sig.=(Old Cog.Sig.*weight1)+(Current Data*weight2)
- In this embodiment, two different weighting values are used (weight1 and weight2). These weighting values represent percentages and, when added together, total 100 percent. In a particular embodiment of the invention, emphasis is placed on the historical data (i.e., the Old Cognitive Signature values). In this embodiment, weight1 is 0.80 and weight2 is 0.20, thereby placing a significant emphasis on the historical data. It will be appreciated that various other weighting values may be used depending on the emphasis desired for historical data. The weighting values may vary between different devices, systems, or applications. As discussed above, in certain situations (e.g., when a serious alarm is generated) the existing cognitive signature is not updated (to avoid improperly skewing the cognitive signature values).
- After updating the cognitive signature, the procedure of FIG. 6B continues to step104 to update the cognitive signature correlation factors. The cognitive signature correlation factors are updated by comparing the current data to the associated cognitive signature. For example, if the current data is within the cognitive signature, then the correlation factor is updated to indicate an increased correlation. Similarly, if the current data is not within the cognitive signature, then the correlation factor is updated to indicate a decreased correlation.
- FIG. 7 illustrates an embodiment of an
analysis module 38.Analysis module 38 includes a network operation andperformance analyzer 110 that monitors a network environment and identifies problems or potential problems in the network environment.Analyzer 110 receivescurrent data 112, one or morecognitive signatures 114, one ormore analysis rules 116,exception information 118, and signature correlation factors 120.Current data 112 is received, for example, from data collection module 30 (shown in FIG. 2). Current data may be communicated toanalysis module 38 via a data link betweendata collection module 30 orstorage device 36, andcurrent data 112.Cognitive signatures 114,exception information 118, and signature correlation factors 120 are received, for example, fromcognitive signature module 34. Analysis rules 116 include one or more rules that compare the current data to one or more cognitive signatures or threshold values. Several exemplary rules are provided below. - If (NetworkUtilization)>(PeakHistoricalUtilization) then Alarm1
- If (NetworkUtilization)>(PeakHistoricalUtilization*1.25) then Alarm2
- If (ApplicationResponseTime)>(Threshold1) then Alarm8
- The first rule generates an alarm (Alarm1) if the current network utilization exceeds the peak historical utilization, as defined by the cognitive signature, for the current time period. Alarm1 indicates the event that caused the alarm (network utilization exceeding peak historical utilization) as well as the network device(s) associated with the parameter (network utilization) associated with the alarm. The second rule generates a different alarm (Alarm2) if the current network utilization exceeds the peak historical utilization by 25 percent. Alarm2 is associated with a more serious event because the current data significantly exceeds the cognitive signature. Thus, if both Alarm1 and Alarm2 are identified by the analysis rules, Alarm1 may be ignored because Alarm2 is a more serious event. The third rule generates an alarm (Alarm8) if a particular application response time exceeds a threshold value (Threshold1). Threshold1 may be a static value that causes an alarm to be generated when the threshold is exceeded, regardless of any cognitive signature associated the application's response time. Thus, analysis rules are used to apply both dynamic cognitive signatures and static threshold values. A particular analysis rule may apply both cognitive signatures and threshold values to one or more network environment parameters.
- Other analysis rules consider signature correlation factors as well as cognitive signatures or threshold values. For example:
- If ((NetworkUtilization)>(PeakHistoricalUtilization)) and ((SignatureCorrelationFactor)>0.8) then Alarm15
- In the above example, the analysis rule generates an alarm (Alarm15) if the current network utilization exceeds the peak historical utilization and the cognitive signature associated with network utilization has a high correlation factor (i.e., above 80 percent). Alarm15 indicates a serious event because network utilization is typically highly correlated, but the current data has exceeded the cognitive signature values for the current time period. An analysis rule may use any combination of current data, cognitive signatures, correlation factors, and exception information.
- Network operation and
performance analyzer 110 shown in FIG. 7 compares the current data with one or more cognitive signatures or thresholds to determine whether a problem or a potential problem exists in the network environment. This comparison is performed by applying one or more analysis rules, as discussed above. If a problem or a potential problem is identified,analyzer 110 communicates information regarding the alarm to an alarm generator or other device responsible for providing notification of the problem or potential problem. The information regarding the alarm is communicated across alink 124. In one embodiment of the invention, the alarm generator takes an appropriate action based on the alarm information received and information contained in a table or other mechanism that associates particular alarm information with a particular action. In another embodiment of the invention, alarm generator may consider other information in addition to the received alarm information when determining the appropriate action. In this embodiment, the alarm generator may contain additional logic or analysis procedures that determine the appropriate action to perform, if any. Additional details regarding the alarm generator is provided below with respect to FIGS. 9 and 10. - Network operation and
performance analyzer 110 is also coupled tonetwork analyzer tools 122.Tools 122 are used to obtain additional information regarding a problem or a potential problem. For example, tools are available to adjust the polling rate of a particular device, system, or application. The polling rate may be adjusted based on network utilization (as network utilization increases, polling may decrease to avoid further congestion of the network communication links). Additionally, the polling rate may be adjusted based on detection of a problem with a particular network device (polling may be increased to closely monitor the operation of the particular network device). Other tools are available to trace a path between two devices or systems in a network environment. For example, if a particular device is not responding, the tool may test all devices, interfaces, and communication links between the network monitor and the particular device. If all other devices, interfaces, and communication links between the network monitor and the non-responsive device are functioning properly, then the problem is with the non-responsive device itself.Network analyzer tools 122 may also include tools for setting threshold values, and creating or modifying analysis rules. - FIG. 8 is a flow diagram illustrating an embodiment of a procedure for analyzing performance or operation of a network environment. At step126, one or more analysis rules are applied to the current data collected from the network. As discussed above, the analysis rules perform various analysis of the current data in relation to cognitive signatures or thresholds. Step 128 determines whether the current data collected from the network is within the associated cognitive signatures. If the current data is within the associated cognitive signatures, the procedure returns to step 126 to await the collection of the next set of data from the network.
- If the current data is not within the associated cognitive signatures, the procedure continues from
step 128 to step 130 to determine the deviation of the current data from the associated cognitive signatures and the duration of the deviation. If the current data deviates only slightly from the cognitive signature, it may be ignored or treated as a minor event. However, if the deviation is significant, the deviation may be treated as an important or serious event. If the duration of the deviation is small (e.g., only a few minutes), the deviation may be ignored or treated as a minor event. But, if the duration of the deviation is significant (e.g., several hours), the deviation may be treated as an important or serious event. Step 132 compares the deviation of the current data to the cognitive signature correlation factors. As discussed above, the signature correlation factors can be used to determine the severity of the deviation based on the historical correlation of the cognitive signature. Althoughsteps - In one embodiment of the invention,
step 128 in FIG. 8 also determines whether the current data is within the cognitive signature for the previous time period or within the cognitive signature for the next time period. Thus,step 128 compares the current data to three different cognitive signatures (i.e., the cognitive signatures for the previous, current, and next time periods). By comparing the current data to the previous time period and the next time period, the procedure is able to identify a pattern or event that is shifted in time. For example, a high network utilization may typically occur between 2:00 p.m. and 3:00 p.m. If a high network utilization occurs between 1:00 p.m. and 2:00 p.m., the procedure may not consider it to be unusual because high network utilization typically occurs during the next time period. By analyzing adjacent cognitive signatures, the procedure is able to avoid generating false alarms when a typical pattern or event has been shifted in time to an adjacent time period. - FIG. 9 illustrates an embodiment of an alarm generator.
Alarm generator 40 includes an alarm analyzer 139 that receives alarm information from an analysis module (e.g.,analysis module 38 in FIG. 2) indicating the type of alarm and the severity of the alarm. The alarm information is received on alink 138. The alarm type may indicate whether the problem is a hardware problem or a software problem, or may indicate the type of device or application in which the problem was identified. The alarm type may also indicate the parameter (e.g., network utilization) that triggered the alarm. The severity of the alarm indicates whether the problem is a significant problem that requires immediate attention, a minor problem that should be monitored, or a moderate problem that should receive attention when a network administrator is available. - Alarm analyzer139 is coupled to alarm
notification policy 140 andalarm action module 141.Alarm notification policy 140 identifies the manner in which a network administrator or other individual is notified of an alarm. Additionally,alarm notification policy 140 may identify a particular action to take in response to an alarm. The manner in which notice is provided may depend on the type of alarm or the severity of the alarm. A severe alarm may cause a network administrator to be paged or otherwise immediately contacted, whereas a minor alarm may provide notice to the network administrator via e-mail or other lower priority mechanism.Alarm action module 141 implements the types of actions to take in response to various alarms. Actions include resetting a network device or application, or deactivating particular interfaces or communication links that are experiencing problems. Based on the received alarm information and the alarm notification policy, alarm analyzer 139 determines how to handle the alarm, and communicates the action to alarmaction module 141. - Alarm analyzer139 is also able to correlate multiple events into a single alarm or a single problem. Certain events are predictable in response to other events. For example, an increase in network utilization generally causes an increase in response time and an increase in network errors. Thus, if network utilization increases significantly and, at approximately the same time, response time increases, then the two events (utilization and response time increase) may be treated as a single event. Similarly, if several devices along a common path experience common problems (e.g., a communication problem on the path), the events may be treated as a singe event rather than multiple individual events. Also, errors on multiple interfaces of a device may be treated as a single event because a problem with the device may be the cause of all interface errors.
-
Alarm action module 141 includes multiple modules capable of communicating an alarm or other problem indicator to a network administrator or other individual or system. Anelectronic mail generator 142 is capable of generating and sending an e-mail message identifying various information about the problem or alarm. For example, the e-mail message may include information regarding the type of problem, the severity of the problem, and the likely source of the problem, if known. The e-mail message is sent to one or more network administrators, managers, or other personnel across acommunication link 144. Apaging module 146 may generate and send a pager message to one or more pagers (e.g., pagers carried by a network administrator or other individual responsible for handling problems in the network environment).Paging module 146 communicates the pager message acrosscommunication link 148. In one embodiment,paging module 146 automatically dials the appropriate pager number and communicates the message to the pager. In another embodiment,paging module 146 communicates the pager number and message to another device (across communication link 148), which then generates the page. - An
alarm communicator 150 is capable of communicating alarm information to another device or system acrosscommunication link 152. Additionally,alarm communicator 150 is capable of activating an application or process, such as an executable code sequence. The application may be located on the network monitor, or on any another device or system in the network environment. The particular application activated is determined by the information contained inalarm notification policy 140 and/oralarm action module 141. Several different applications may be executed depending on the type of alarm, source of the problem, or type of parameter that triggered the alarm. For example,alarm communicator 150 can reset a device, subsystem or component that may be the source of a problem. After taking this action,analysis module 38 will analyze network operation and performance to determine whether the problem has been corrected. - FIG. 10 is a flow diagram illustrating an embodiment of a procedure for generating an alarm based on analysis of the network environment. At
step 160, alarm information is received from an analysis module (e.g.,analysis module 38 in FIG. 2). Step 162 identifies the type of problem, the severity of the problem, the source of the problem (if known), and the event or activity that triggered the alarm. Step 164 then determines the appropriate action to take, if any, based on the received alarm information and the alarm notification policy. The appropriate action may include generating a pager message, an e-mail message, or activating another application or procedure. For example, an e-mail message can be used to communicate information regarding minor problems or other events that do not require immediate attention. A pager message is generated for all important alarms and all serious alarms, such that a network administrator or other individual is immediately notified of the problem. An application can be activated by the alarm generator to take an action appropriate for the alarm. -
Step 165 determines whether any action is required. If the alarm is a minor alarm, the alarm generator may ignore the alarm and not take action, unless the alarm continues for a significant period of time or increases in severity. If action is required, the procedure continues to step 166, which branches to one of three different steps depending on the appropriate action determined instep 164. If the appropriate action is an e-mail, the procedure branches to step 168, which generates and sends an e-mail message to the appropriate recipients. If the appropriate action is a pager message, the procedure branches to step 170, which generates and sends a pager message to the appropriate recipients. If the appropriate action is the communication of alarm information to another device or application, the procedure branches to step 172, which communicates alarm information to another system or application. Step 172 may also activate an application or procedure on the network monitor or other device in the network environment. Althoughsteps - FIG. 11 illustrates an embodiment of a computer system that can be used with the present invention. For example, embodiments of the invention may use a computer of the type shown in FIG. 11 for a network monitor, a network device, a server, or any other device contained in or used with the monitoring system discussed above. The various components in FIG. 11 are provided by way of example. Certain components of the computer in FIG. 11 can be deleted for particular implementations of the invention. The computer system shown in FIG. 11 may be any type of computer, including a general purpose computer.
- FIG. 11 illustrates a
system bus 200 to which various components and devices are coupled. Aprocessor 202 performs the processing tasks required by the computer.Processor 202 may be any type of processing device capable of implementing the steps necessary to perform the various procedures and operations discussed above. An Input/Output (I/O)device 204 provides a mechanism for communicating with other devices coupled to the computer. A Read-Only Memory (ROM) 206 and a Random Access Memory (RAM) 208 provide a storage mechanism for various data and information used by the computer. AlthoughROM 206 andRAM 208 are shown coupled tobus 200, in alternate embodiments,ROM 206 andRAM 208 are coupled directly toprocessor 202 or coupled to a dedicated memory bus (not shown). - A
video display 210 displays various information and data to the user of the computer. Adisk drive 212 provides a mechanism for the long-term mass storage of information. Aninput device 214 and apointing device 216 allow the user of the computer to enter information and commands to the computer system.Input device 214 may be, for example, a keyboard, keypad, handwriting recognition device, or voice recognition device.Pointing device 216 includes, for example, a mouse, track ball, or touch pad. Aprinter 218 is capable of creating a hard copy of information generated by or used by the computer. - Embodiments of the present invention may be implemented using a computer-readable medium (also referred to as a processor-readable medium) containing various sets of instructions, code sequences, configuration information, and other data used by a computer or other processing device. The various information stored on the computer-readable medium is used to perform various monitoring, analysis, communication, and processing operations, such as those described above. The computer-readable medium may be any type of magnetic, optical, or electrical storage medium including a diskette, magnetic tape, CD-ROM, memory device, or other storage medium.
- From the above description and drawings, it will be understood by those of ordinary skill in the art that the particular embodiments shown and described are for purposes of illustration only and are not intended to limit the scope of the invention. Those of ordinary skill in the art will recognize that the invention may be embodied in other specific forms without departing from its spirit or essential characteristics. References to details of particular embodiments are not intended to limit the scope of the claims.
Claims (46)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/067,319 US6327677B1 (en) | 1998-04-27 | 1998-04-27 | Method and apparatus for monitoring a network environment |
Publications (1)
Publication Number | Publication Date |
---|---|
US20010052087A1 true US20010052087A1 (en) | 2001-12-13 |
Family
ID=22075199
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/067,319 Expired - Lifetime US6327677B1 (en) | 1998-04-27 | 1998-04-27 | Method and apparatus for monitoring a network environment |
US09/067,319 Granted US20010052087A1 (en) | 1998-04-27 | 1998-04-27 | Method and apparatus for monitoring a network environment |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/067,319 Expired - Lifetime US6327677B1 (en) | 1998-04-27 | 1998-04-27 | Method and apparatus for monitoring a network environment |
Country Status (1)
Country | Link |
---|---|
US (2) | US6327677B1 (en) |
Cited By (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020053018A1 (en) * | 2000-06-12 | 2002-05-02 | Kenji Ota | Apparatus and method to identify computer system |
US20020107958A1 (en) * | 2000-10-31 | 2002-08-08 | Faraldo David D. | Method of and apparatus for notification of state changes in a monitored system |
US6591377B1 (en) * | 1999-11-24 | 2003-07-08 | Unisys Corporation | Method for comparing system states at different points in time |
US20030172152A1 (en) * | 2002-03-11 | 2003-09-11 | Qwest Communications International Inc. | Automated module tracking system for communications networks |
US20030172153A1 (en) * | 2002-03-11 | 2003-09-11 | Qwest Communications International Inc. | Systems and methods for tracking the reliability of communications networks |
US20040103185A1 (en) * | 2002-11-21 | 2004-05-27 | Combs Nathan Hideaki | Adaptive self-repair and configuration in distributed systems |
US20040193956A1 (en) * | 2003-03-28 | 2004-09-30 | International Business Machines Corporation | System, method and program product for checking a health of a computer system |
US20050172306A1 (en) * | 2003-10-20 | 2005-08-04 | Agarwal Manoj K. | Systems, methods and computer programs for determining dependencies between logical components in a data processing system or network |
US6950868B1 (en) * | 2000-10-31 | 2005-09-27 | Red Hat, Inc. | Method of and apparatus for remote monitoring |
US20060142001A1 (en) * | 2004-12-28 | 2006-06-29 | Moisan Kevin J | Methods and apparatus for monitoring a communication network |
US20060152355A1 (en) * | 2004-12-27 | 2006-07-13 | Asuman Suenbuel | False alarm mitigation using a sensor network |
US7107339B1 (en) * | 2001-04-07 | 2006-09-12 | Webmethods, Inc. | Predictive monitoring and problem identification in an information technology (IT) infrastructure |
US20070019548A1 (en) * | 2005-07-22 | 2007-01-25 | Balachander Krishnamurthy | Method and apparatus for data network sampling |
US20070064736A1 (en) * | 2005-09-19 | 2007-03-22 | Fujitsu Network Communications | Zero suppressed performance management data interpretation and same value suppression and interpretation |
US20070165541A1 (en) * | 2005-07-13 | 2007-07-19 | John Arpee | System and method for data maintenance and integration including interpolation |
US20070297001A1 (en) * | 2006-06-22 | 2007-12-27 | Brian Podl | Multi-function peripheral remote alert notification system and method |
US20080133749A1 (en) * | 2002-11-08 | 2008-06-05 | Federal Network Systems, Llc | Server resource management, analysis, and intrusion negation |
US20080137549A1 (en) * | 2006-12-08 | 2008-06-12 | At&T Knowledge Ventures, Lp | System and method of managing network performance |
US20080222727A1 (en) * | 2002-11-08 | 2008-09-11 | Federal Network Systems, Llc | Systems and methods for preventing intrusion at a web host |
US7457722B1 (en) | 2004-11-17 | 2008-11-25 | Symantec Operating Corporation | Correlation of application instance life cycle events in performance monitoring |
US20090013220A1 (en) * | 2005-04-20 | 2009-01-08 | Mitsubishi Electric Corporation | Data Collecting Apparatus and Gateway Apparatus |
US7904457B2 (en) | 2007-05-30 | 2011-03-08 | International Business Machines Corporation | Semantic correlation for flow analysis in messaging systems |
US20110153788A1 (en) * | 2009-12-23 | 2011-06-23 | Jacobus Van Der Merwe | Method and System for Automated Network Operations |
US20120079325A1 (en) * | 2010-09-29 | 2012-03-29 | Sepaton, Inc. | System Health Monitor |
US20120113814A1 (en) * | 2009-07-14 | 2012-05-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Method And Arrangement In A Telecommunication System |
US8224942B1 (en) * | 2007-10-02 | 2012-07-17 | Google Inc. | Network failure detection |
US20120282933A1 (en) * | 2010-02-01 | 2012-11-08 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US8451731B1 (en) | 2007-07-25 | 2013-05-28 | Xangati, Inc. | Network monitoring using virtual packets |
US8601578B1 (en) * | 2011-01-20 | 2013-12-03 | Google Inc. | Identifying potentially suspicious business listings for moderation |
US8600915B2 (en) | 2011-12-19 | 2013-12-03 | Go Daddy Operating Company, LLC | Systems for monitoring computer resources |
US8639797B1 (en) * | 2007-08-03 | 2014-01-28 | Xangati, Inc. | Network monitoring of behavior probability density |
US8719196B2 (en) | 2011-12-19 | 2014-05-06 | Go Daddy Operating Company, LLC | Methods for monitoring computer resources using a first and second matrix, and a feature relationship tree |
GB2523629A (en) * | 2013-12-19 | 2015-09-02 | Bae Systems Plc | Network faul detection and location |
US9158847B1 (en) * | 2011-07-19 | 2015-10-13 | Kyndi Inc. | Cognitive memory encoding networks for fast semantic indexing storage and retrieval |
US20170141996A1 (en) * | 2015-11-18 | 2017-05-18 | Gigamon Inc. | Routing network traffic packets through a shared inline tool |
CN107862866A (en) * | 2017-11-06 | 2018-03-30 | 浙江工商大学 | Noise data point detecting method based on the translation of mean deviation amount |
US10009263B1 (en) | 2015-10-09 | 2018-06-26 | Gigamon Inc. | Network switch device for routing network traffic through an inline tool |
CN109688188A (en) * | 2018-09-07 | 2019-04-26 | 平安科技(深圳)有限公司 | Monitoring alarm method, apparatus, equipment and computer readable storage medium |
US10992555B2 (en) | 2009-05-29 | 2021-04-27 | Virtual Instruments Worldwide, Inc. | Recording, replay, and sharing of live network monitoring views |
EP3905591A4 (en) * | 2018-12-29 | 2022-02-16 | Wangsu Science & Technology Co., Ltd. | Server abnormality processing method and management device |
US11449407B2 (en) | 2020-05-28 | 2022-09-20 | Bank Of America Corporation | System and method for monitoring computing platform parameters and dynamically generating and deploying monitoring packages |
Families Citing this family (264)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6393497B1 (en) | 1998-03-20 | 2002-05-21 | Sun Microsystems, Inc. | Downloadable smart proxies for performing processing associated with a remote procedure call in a distributed system |
US6466947B2 (en) * | 1998-03-20 | 2002-10-15 | Sun Microsystems, Inc. | Apparatus and method for dynamically verifying information in a distributed system |
US6185611B1 (en) | 1998-03-20 | 2001-02-06 | Sun Microsystem, Inc. | Dynamic lookup service in a distributed system |
US7249344B1 (en) | 1996-10-31 | 2007-07-24 | Citicorp Development Center, Inc. | Delivery of financial services to remote devices |
US5867153A (en) | 1996-10-30 | 1999-02-02 | Transaction Technology, Inc. | Method and system for automatically harmonizing access to a software application program via different access devices |
US8112330B1 (en) | 1997-08-07 | 2012-02-07 | Citibank Development Center, Inc. | System and method for delivering financial services |
US7668781B2 (en) | 1996-10-31 | 2010-02-23 | Citicorp Development Center, Inc. | Global method and system for providing enhanced transactional functionality through a customer terminal |
US7502752B1 (en) * | 1997-08-07 | 2009-03-10 | Citicorp Development Center, Inc. | System and method for delivering financial services |
WO1999044296A2 (en) * | 1998-02-26 | 1999-09-02 | Sun Microsystems, Inc. | Apparatus and method for dynamically verifying information in a distributed system |
US20020046228A1 (en) * | 1998-03-20 | 2002-04-18 | Sun Microsystems, Inc. | Method and system for facilitating access to a lookup service |
US20030120775A1 (en) * | 1998-06-15 | 2003-06-26 | Compaq Computer Corporation | Method and apparatus for sending address in the message for an e-mail notification action to facilitate remote management of network devices |
US6453346B1 (en) * | 1998-07-17 | 2002-09-17 | Proactivenet, Inc. | Method and apparatus for intelligent storage and reduction of network information |
JP3980768B2 (en) * | 1998-09-02 | 2007-09-26 | 株式会社日立製作所 | Distributed processing system and cooperative method thereof |
US6836800B1 (en) * | 1998-09-30 | 2004-12-28 | Netscout Systems, Inc. | Managing computer resources |
US6591255B1 (en) | 1999-04-05 | 2003-07-08 | Netuitive, Inc. | Automatic data extraction, error correction and forecasting system |
US7685311B2 (en) * | 1999-05-03 | 2010-03-23 | Digital Envoy, Inc. | Geo-intelligent traffic reporter |
US6757740B1 (en) | 1999-05-03 | 2004-06-29 | Digital Envoy, Inc. | Systems and methods for determining collecting and using geographic locations of internet users |
US20060224752A1 (en) * | 1999-05-03 | 2006-10-05 | Parekh Sanjay M | Determining geographic locations of private network Internet users |
US7844729B1 (en) | 1999-05-03 | 2010-11-30 | Digital Envoy, Inc. | Geo-intelligent traffic manager |
US6457015B1 (en) | 1999-05-07 | 2002-09-24 | Network Appliance, Inc. | Adaptive and generalized status monitor |
WO2000072183A2 (en) | 1999-05-24 | 2000-11-30 | Aprisma Management Technologies, Inc. | Service level management |
GB2350983B (en) * | 1999-06-10 | 2001-10-03 | 3Com Corp | Network problem indication |
JP2000358029A (en) * | 1999-06-15 | 2000-12-26 | Nec Corp | Automatic fault diagnostic network system, and automatic fault diagnostic method for network |
US6718535B1 (en) | 1999-07-30 | 2004-04-06 | Accenture Llp | System, method and article of manufacture for an activity framework design in an e-commerce based environment |
US6704873B1 (en) | 1999-07-30 | 2004-03-09 | Accenture Llp | Secure gateway interconnection in an e-commerce based environment |
US7126716B1 (en) * | 1999-08-20 | 2006-10-24 | Zih Corp. | Printer for printing labels, tags or the like |
US6961749B1 (en) | 1999-08-25 | 2005-11-01 | Network Appliance, Inc. | Scalable file server with highly available pairs |
US6883120B1 (en) * | 1999-12-03 | 2005-04-19 | Network Appliance, Inc. | Computer assisted automatic error detection and diagnosis of file servers |
US6704883B1 (en) * | 1999-12-22 | 2004-03-09 | Cisco Systems, Inc. | Event-enabled distributed testing system |
US6985901B1 (en) | 1999-12-23 | 2006-01-10 | Accenture Llp | Controlling data collection, manipulation and storage on a network with service assurance capabilities |
US6909696B1 (en) * | 2000-01-21 | 2005-06-21 | Verizon Corporate Services Group Inc. | Systems and methods for visualizing a communications network |
US6920110B2 (en) * | 2001-02-14 | 2005-07-19 | Microsoft Corporation | System and method for transferring data over a network |
US7437428B1 (en) * | 2000-02-16 | 2008-10-14 | Microsoft Corporation | System and method for transferring data over a network |
US6862623B1 (en) * | 2000-04-14 | 2005-03-01 | Microsoft Corporation | Capacity planning for server resources |
US6792455B1 (en) * | 2000-04-28 | 2004-09-14 | Microsoft Corporation | System and method for implementing polling agents in a client management tool |
US6889255B1 (en) * | 2000-04-28 | 2005-05-03 | Microsoft Corporation | System and method for caching data in a client management tool |
US7039695B1 (en) * | 2000-04-28 | 2006-05-02 | Microsoft Corporation | System and method for archiving within a client management tool |
US7523180B1 (en) * | 2000-04-28 | 2009-04-21 | Microsoft Corporation | System and method for service chain management in a client management tool |
US7490145B2 (en) * | 2000-06-21 | 2009-02-10 | Computer Associates Think, Inc. | LiveException system |
US6678837B1 (en) * | 2000-06-30 | 2004-01-13 | Intel Corporation | Processor control flow monitoring using a signature table for soft error detection |
JP3654151B2 (en) * | 2000-07-17 | 2005-06-02 | 日本電気株式会社 | Maintenance information notification method and system using portable terminal, and recording medium |
US7051243B2 (en) * | 2002-04-30 | 2006-05-23 | Sun Microsystems, Inc. | Rules-based configuration problem detection |
US6973491B1 (en) * | 2000-08-09 | 2005-12-06 | Sun Microsystems, Inc. | System and method for monitoring and managing system assets and asset configurations |
US6662318B1 (en) * | 2000-08-10 | 2003-12-09 | International Business Machines Corporation | Timely error data acquistion |
US6816898B1 (en) * | 2000-08-16 | 2004-11-09 | Proactivenet, Inc. | Interfacing external metrics into a performance management system |
US7003559B1 (en) * | 2000-10-23 | 2006-02-21 | Hewlett-Packard Development Company, L.P. | System and method for determining probable network paths between nodes in a network topology |
US6876988B2 (en) | 2000-10-23 | 2005-04-05 | Netuitive, Inc. | Enhanced computer performance forecasting system |
US20020077792A1 (en) * | 2000-10-27 | 2002-06-20 | Panacya, Inc. | Early warning in e-service management systems |
US7225250B1 (en) * | 2000-10-30 | 2007-05-29 | Agilent Technologies, Inc. | Method and system for predictive enterprise resource management |
JP3885483B2 (en) * | 2000-10-30 | 2007-02-21 | 富士通株式会社 | Service execution method and apparatus |
US7346928B1 (en) | 2000-12-01 | 2008-03-18 | Network Appliance, Inc. | Decentralized appliance virus scanning |
US7778981B2 (en) | 2000-12-01 | 2010-08-17 | Netapp, Inc. | Policy engine to control the servicing of requests received by a storage server |
US6834304B1 (en) * | 2000-12-21 | 2004-12-21 | Nortel Networks Limited | Method and apparatus for creating a network audit report |
US20020104047A1 (en) * | 2001-01-31 | 2002-08-01 | Ncr Corporation | Financial document processing system and method of operating a financial document processing system |
US7120678B2 (en) * | 2001-02-27 | 2006-10-10 | Hewlett-Packard Development Company, L.P. | Method and apparatus for configurable data collection on a computer network |
US8478824B2 (en) * | 2002-02-05 | 2013-07-02 | Portauthority Technologies Inc. | Apparatus and method for controlling unauthorized dissemination of electronic mail |
US7681032B2 (en) * | 2001-03-12 | 2010-03-16 | Portauthority Technologies Inc. | System and method for monitoring unauthorized transport of digital content |
US20050025291A1 (en) * | 2001-03-12 | 2005-02-03 | Vidius Inc. | Method and system for information distribution management |
AU2002305889A1 (en) * | 2001-06-08 | 2002-12-23 | Netuitive, Inc. | Automated analyzers for estimation systems |
JP2003006063A (en) * | 2001-06-22 | 2003-01-10 | Nec Corp | Communication monitoring system and monitoring server |
JP2003006068A (en) * | 2001-06-26 | 2003-01-10 | Canon Inc | Network device managing device, managing method and management program |
US7076695B2 (en) * | 2001-07-20 | 2006-07-11 | Opnet Technologies, Inc. | System and methods for adaptive threshold determination for performance metrics |
US20030023716A1 (en) * | 2001-07-25 | 2003-01-30 | Loyd Aaron Joel | Method and device for monitoring the performance of a network |
JP4294912B2 (en) * | 2001-08-13 | 2009-07-15 | ブラザー工業株式会社 | Terminal information notification system, terminal information notification method, and network terminal device |
US7756969B1 (en) | 2001-09-07 | 2010-07-13 | Oracle America, Inc. | Dynamic provisioning of identification services in a distributed system |
US7660887B2 (en) | 2001-09-07 | 2010-02-09 | Sun Microsystems, Inc. | Systems and methods for providing dynamic quality of service for a distributed system |
US20030051030A1 (en) * | 2001-09-07 | 2003-03-13 | Clarke James B. | Distributed metric discovery and collection in a distributed system |
US20030051029A1 (en) | 2001-09-07 | 2003-03-13 | Reedy Dennis G. | Dynamic provisioning of sevice components in a distributed system |
US7490146B1 (en) * | 2001-09-17 | 2009-02-10 | Ricoh Company, Ltd. | System, method, and computer program product for collecting and sending various types of information to a monitor using e-mail |
JP2003114811A (en) * | 2001-10-05 | 2003-04-18 | Nec Corp | Method and system for automatic failure recovery and apparatus and program therefor |
US7003688B1 (en) | 2001-11-15 | 2006-02-21 | Xiotech Corporation | System and method for a reserved memory area shared by all redundant storage controllers |
US6996741B1 (en) | 2001-11-15 | 2006-02-07 | Xiotech Corporation | System and method for redundant communication between redundant controllers |
US7127633B1 (en) | 2001-11-15 | 2006-10-24 | Xiotech Corporation | System and method to failover storage area network targets from one interface to another |
US7043663B1 (en) | 2001-11-15 | 2006-05-09 | Xiotech Corporation | System and method to monitor and isolate faults in a storage area network |
US6883065B1 (en) | 2001-11-15 | 2005-04-19 | Xiotech Corporation | System and method for a redundant communication channel via storage area network back-end |
FR2832577B1 (en) * | 2001-11-16 | 2005-03-18 | Cit Alcatel | ADAPTIVE DATA ACQUISITION FOR NETWORK OR SERVICE MANAGEMENT SYSTEMS |
US7355981B2 (en) * | 2001-11-23 | 2008-04-08 | Apparent Networks, Inc. | Signature matching methods and apparatus for performing network diagnostics |
US7000154B1 (en) * | 2001-11-28 | 2006-02-14 | Intel Corporation | System and method for fault detection and recovery |
CA2365430A1 (en) * | 2001-12-19 | 2003-06-19 | Alcatel Canada Inc. | System and method for collecting statistics for a communication network |
US7280988B2 (en) * | 2001-12-19 | 2007-10-09 | Netuitive, Inc. | Method and system for analyzing and predicting the performance of computer network using time series measurements |
DE10162987A1 (en) * | 2001-12-20 | 2003-07-17 | Siemens Ag | Network Performance Management |
TW554277B (en) * | 2001-12-28 | 2003-09-21 | Inventec Corp | Automated network management system |
US20040153692A1 (en) * | 2001-12-28 | 2004-08-05 | O'brien Michael | Method for managing faults it a computer system enviroment |
US7299277B1 (en) * | 2002-01-10 | 2007-11-20 | Network General Technology | Media module apparatus and method for use in a network monitoring environment |
US6801940B1 (en) * | 2002-01-10 | 2004-10-05 | Networks Associates Technology, Inc. | Application performance monitoring expert |
US20030140150A1 (en) * | 2002-01-14 | 2003-07-24 | Dean Kemp | Self-monitoring service system with reporting of asset changes by time and category |
US7362701B2 (en) * | 2002-01-14 | 2008-04-22 | Sun Microsystems, Inc. | Customer-based service system including a cascaded pipeline with self-monitoring relays |
US20030135575A1 (en) * | 2002-01-14 | 2003-07-17 | Richard Marejka | Self-monitoring and trending service system with cascaded pipeline linking numerous client systems |
US20030169462A1 (en) * | 2002-03-11 | 2003-09-11 | Netaphor Software, Inc. | System and method for managing network devices |
US20030204588A1 (en) * | 2002-04-30 | 2003-10-30 | International Business Machines Corporation | System for monitoring process performance and generating diagnostic recommendations |
US7363543B2 (en) * | 2002-04-30 | 2008-04-22 | International Business Machines Corporation | Method and apparatus for generating diagnostic recommendations for enhancing process performance |
DE10224209B4 (en) * | 2002-05-31 | 2004-09-23 | Infineon Technologies Ag | Authorization means security module terminal system |
US7131037B1 (en) | 2002-06-05 | 2006-10-31 | Proactivenet, Inc. | Method and system to correlate a specific alarm to one or more events to identify a possible cause of the alarm |
US7234157B2 (en) * | 2002-06-27 | 2007-06-19 | Lenovo Singapore Pte Ltd | Remote authentication caching on a trusted client or gateway system |
US7031884B1 (en) | 2002-07-12 | 2006-04-18 | Netscout Systems, Inc. | System and method for analyzing data streams |
US7243145B1 (en) * | 2002-09-30 | 2007-07-10 | Electronic Data Systems Corporation | Generation of computer resource utilization data per computer application |
US7437446B2 (en) | 2002-09-30 | 2008-10-14 | Electronic Data Systems Corporation | Reporting of abnormal computer resource utilization data |
JP4167876B2 (en) * | 2002-10-03 | 2008-10-22 | 株式会社日立製作所 | Network measurement setting device |
US7478398B2 (en) * | 2002-10-31 | 2009-01-13 | Hewlett-Packard Development Company, L.P. | Management apparatus and method for data collection including accumulating messages and determining message handlers for processing the accumulated messages |
US20040111510A1 (en) * | 2002-12-06 | 2004-06-10 | Shahid Shoaib | Method of dynamically switching message logging schemes to improve system performance |
US7428300B1 (en) | 2002-12-09 | 2008-09-23 | Verizon Laboratories Inc. | Diagnosing fault patterns in telecommunication networks |
US20040120706A1 (en) * | 2002-12-20 | 2004-06-24 | Kerry Johnson | Fault isolation in agile transparent networks |
US7298755B2 (en) | 2003-02-08 | 2007-11-20 | Hewlett-Packard Development Company, L.P. | Apparatus and method for communicating with a network and for monitoring operational performance of the apparatus |
US7958215B2 (en) * | 2003-02-12 | 2011-06-07 | International Business Machines Corporation | System management using real time collaboration |
KR100860157B1 (en) * | 2003-04-14 | 2008-09-24 | 텔케미, 인코포레이티드 | System for identifying and locating network problems |
AU2003233206A1 (en) * | 2003-04-30 | 2004-11-23 | Telecom Italia S.P.A. | Method, system and computer program product for evaluating download performance of web pages |
US7421495B2 (en) * | 2003-06-27 | 2008-09-02 | Computer Associates Think, Inc. | System and method for monitoring network devices |
US7493562B2 (en) * | 2003-06-27 | 2009-02-17 | Computer Associates Think, Inc. | System and method for bridge port administration |
US7730174B2 (en) | 2003-06-27 | 2010-06-01 | Computer Associates Think, Inc. | System and method for agent-based monitoring of network devices |
US7237266B2 (en) * | 2003-06-30 | 2007-06-26 | At&T Intellectual Property, Inc. | Electronic vulnerability and reliability assessment |
US20050038697A1 (en) * | 2003-06-30 | 2005-02-17 | Aaron Jeffrey A. | Automatically facilitated marketing and provision of electronic services |
US7409593B2 (en) * | 2003-06-30 | 2008-08-05 | At&T Delaware Intellectual Property, Inc. | Automated diagnosis for computer networks |
US7269757B2 (en) * | 2003-07-11 | 2007-09-11 | Reflectent Software, Inc. | Distributed computer monitoring system and methods for autonomous computer management |
US20050076113A1 (en) * | 2003-09-12 | 2005-04-07 | Finisar Corporation | Network analysis sample management process |
US7299367B2 (en) * | 2003-11-07 | 2007-11-20 | International Business Machines Corporation | Methods, systems and computer program products for developing resource monitoring systems from observational data |
US7302379B2 (en) * | 2003-12-07 | 2007-11-27 | Adaptive Spectrum And Signal Alignment, Inc. | DSL system estimation and parameter recommendation |
US8031761B2 (en) * | 2003-12-07 | 2011-10-04 | Adaptive Spectrum And Signal Alignment, Inc. | Adaptive margin and band control |
US20050138642A1 (en) * | 2003-12-18 | 2005-06-23 | International Business Machines Corporation | Event correlation system and method for monitoring resources |
US7792874B1 (en) | 2004-01-30 | 2010-09-07 | Oracle America, Inc. | Dynamic provisioning for filtering and consolidating events |
CN101036343A (en) * | 2004-04-16 | 2007-09-12 | 阿派伦特网络股份有限公司 | Method and apparatus for automating and scaling active probing-based IP network performance monitoring and diagnosis |
US7457855B2 (en) * | 2004-04-30 | 2008-11-25 | Aol Llc | Network configuration management |
US7359831B2 (en) * | 2004-05-21 | 2008-04-15 | Bea Systems, Inc. | Diagnostic context |
US7379849B2 (en) * | 2004-05-21 | 2008-05-27 | Bea Systems, Inc. | Diagnostic image |
US8490064B2 (en) * | 2004-05-21 | 2013-07-16 | Oracle International Corporation | Hierarchical debug |
US7376534B2 (en) * | 2004-05-21 | 2008-05-20 | Bea Systems, Inc. | Watches and notifications |
JP4328672B2 (en) * | 2004-06-01 | 2009-09-09 | キヤノン株式会社 | Information processing apparatus and device |
US7263636B1 (en) * | 2004-06-10 | 2007-08-28 | Sprint Communications Company L.P. | Circuit-trending system and method |
US7617501B2 (en) | 2004-07-09 | 2009-11-10 | Quest Software, Inc. | Apparatus, system, and method for managing policies on a computer having a foreign operating system |
JP4390649B2 (en) * | 2004-07-14 | 2009-12-24 | 富士通株式会社 | Network loop detector |
FR2874148B1 (en) * | 2004-08-05 | 2006-11-24 | Evolium Sas Soc Par Actions Si | METHOD AND SYSTEM FOR OPERATING A CELLULAR MOBILE COMMUNICATIONS NETWORK |
JP4125274B2 (en) * | 2004-08-26 | 2008-07-30 | キヤノン株式会社 | Image input / output device, information processing method, computer-readable storage medium storing program, and program |
US20060063521A1 (en) * | 2004-09-21 | 2006-03-23 | Benjamin Cheung | Method of monitoring wireless network performance |
US7653742B1 (en) | 2004-09-28 | 2010-01-26 | Entrust, Inc. | Defining and detecting network application business activities |
US20060165004A1 (en) * | 2004-11-15 | 2006-07-27 | Steele Mark A | Method and system to analyze digital cross-connect system equipment and software |
KR100628317B1 (en) * | 2004-12-03 | 2006-09-27 | 한국전자통신연구원 | Apparatus for detecting attacks toward network and method thereof |
US8218477B2 (en) * | 2005-03-31 | 2012-07-10 | Alcatel Lucent | Method of detecting wireless network faults |
US8719399B2 (en) * | 2005-04-07 | 2014-05-06 | Opanga Networks, Inc. | Adaptive file delivery with link profiling system and method |
US8909807B2 (en) | 2005-04-07 | 2014-12-09 | Opanga Networks, Inc. | System and method for progressive download using surplus network capacity |
US8589508B2 (en) | 2005-04-07 | 2013-11-19 | Opanga Networks, Inc. | System and method for flow control in an adaptive file delivery system |
US9065595B2 (en) | 2005-04-07 | 2015-06-23 | Opanga Networks, Inc. | System and method for peak flow detection in a communication network |
US11258531B2 (en) | 2005-04-07 | 2022-02-22 | Opanga Networks, Inc. | System and method for peak flow detection in a communication network |
US7500010B2 (en) | 2005-04-07 | 2009-03-03 | Jeffrey Paul Harrang | Adaptive file delivery system and method |
US7849165B2 (en) | 2005-04-21 | 2010-12-07 | Fiducci Thomas E | Data backup, storage, transfer, and retrieval system, method and computer program product |
US8126990B2 (en) | 2005-04-21 | 2012-02-28 | Fiducci Thomas E | Data backup and transfer system, method and computer program product |
US7502846B2 (en) * | 2005-06-07 | 2009-03-10 | Azaleos Corporation | Monitoring service with inter-enterprise contextual analysis |
US20080133746A1 (en) * | 2005-06-08 | 2008-06-05 | Azaleos Corporation | Monitoring service with inter-enterprise contextual analysis |
US20060282530A1 (en) * | 2005-06-14 | 2006-12-14 | Klein Stephen D | Methods and apparatus for end-user based service monitoring |
US7295950B2 (en) * | 2005-06-23 | 2007-11-13 | International Business Machines Corporation | Monitoring multiple channels of data from real time process to detect recent abnormal behavior |
US7783745B1 (en) * | 2005-06-27 | 2010-08-24 | Entrust, Inc. | Defining and monitoring business rhythms associated with performance of web-enabled business processes |
US8463899B2 (en) * | 2005-07-29 | 2013-06-11 | Bmc Software, Inc. | System, method and computer program product for optimized root cause analysis |
US7523352B2 (en) * | 2005-09-09 | 2009-04-21 | International Business Machines Corporation | System and method for examining remote systems and gathering debug data in real time |
JP2007094455A (en) * | 2005-09-26 | 2007-04-12 | Brother Ind Ltd | Network system, printer, and printer control program |
WO2007044326A2 (en) | 2005-10-04 | 2007-04-19 | Adaptive Spectrum And Signal Alignment, Inc. | Dsl system |
US8082349B1 (en) | 2005-10-21 | 2011-12-20 | Entrust, Inc. | Fraud protection using business process-based customer intent analysis |
US7904949B2 (en) | 2005-12-19 | 2011-03-08 | Quest Software, Inc. | Apparatus, systems and methods to provide authentication services to a legacy application |
US7593409B2 (en) * | 2005-12-29 | 2009-09-22 | Honeywell International Inc. | Apparatus and methods for monitoring network traffic |
US20070168505A1 (en) * | 2006-01-19 | 2007-07-19 | Hewlett-Packard Development Company, L.P. | Performance monitoring in a network |
US8087075B2 (en) | 2006-02-13 | 2011-12-27 | Quest Software, Inc. | Disconnected credential validation using pre-fetched service tickets |
US20070233848A1 (en) * | 2006-03-28 | 2007-10-04 | International Business Machines Corporation | Monitor management that enables enhanced data collection |
US8849109B2 (en) * | 2006-03-30 | 2014-09-30 | Alcatel Lucent | Fault isolation and provisioning for optical switches |
US7528981B2 (en) * | 2006-04-27 | 2009-05-05 | Fujifilm Graphics Systems U.S.A., Inc. | System and method for remote monitoring of print systems |
US8429712B2 (en) | 2006-06-08 | 2013-04-23 | Quest Software, Inc. | Centralized user authentication system apparatus and method |
US8194643B2 (en) | 2006-10-19 | 2012-06-05 | Embarq Holdings Company, Llc | System and method for monitoring the connection of an end-user to a remote network |
US8289965B2 (en) | 2006-10-19 | 2012-10-16 | Embarq Holdings Company, Llc | System and method for establishing a communications session with an end-user based on the state of a network connection |
US20080002711A1 (en) * | 2006-06-30 | 2008-01-03 | Bugenhagen Michael K | System and method for access state based service options |
US8488447B2 (en) | 2006-06-30 | 2013-07-16 | Centurylink Intellectual Property Llc | System and method for adjusting code speed in a transmission path during call set-up due to reduced transmission performance |
US8477614B2 (en) | 2006-06-30 | 2013-07-02 | Centurylink Intellectual Property Llc | System and method for routing calls if potential call paths are impaired or congested |
US8717911B2 (en) | 2006-06-30 | 2014-05-06 | Centurylink Intellectual Property Llc | System and method for collecting network performance information |
WO2008005393A2 (en) * | 2006-06-30 | 2008-01-10 | Embarq Holdings Company Llc | System and method for managing subscriber usage of a communications network |
US8000318B2 (en) | 2006-06-30 | 2011-08-16 | Embarq Holdings Company, Llc | System and method for call routing based on transmission performance of a packet network |
US7948909B2 (en) * | 2006-06-30 | 2011-05-24 | Embarq Holdings Company, Llc | System and method for resetting counters counting network performance information at network communications devices on a packet network |
JP4151985B2 (en) * | 2006-07-19 | 2008-09-17 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Technology to detect information processing devices that have malfunctioned |
US8341260B2 (en) * | 2006-08-16 | 2012-12-25 | Oracle America, Inc. | Method and system for identification of decisive action state of server components via telemetric condition tracking |
US7940735B2 (en) | 2006-08-22 | 2011-05-10 | Embarq Holdings Company, Llc | System and method for selecting an access point |
US8107366B2 (en) | 2006-08-22 | 2012-01-31 | Embarq Holdings Company, LP | System and method for using centralized network performance tables to manage network communications |
US8407765B2 (en) | 2006-08-22 | 2013-03-26 | Centurylink Intellectual Property Llc | System and method for restricting access to network performance information tables |
US8144586B2 (en) | 2006-08-22 | 2012-03-27 | Embarq Holdings Company, Llc | System and method for controlling network bandwidth with a connection admission control engine |
US8531954B2 (en) | 2006-08-22 | 2013-09-10 | Centurylink Intellectual Property Llc | System and method for handling reservation requests with a connection admission control engine |
US8130793B2 (en) | 2006-08-22 | 2012-03-06 | Embarq Holdings Company, Llc | System and method for enabling reciprocal billing for different types of communications over a packet network |
US8144587B2 (en) | 2006-08-22 | 2012-03-27 | Embarq Holdings Company, Llc | System and method for load balancing network resources using a connection admission control engine |
US8189468B2 (en) | 2006-10-25 | 2012-05-29 | Embarq Holdings, Company, LLC | System and method for regulating messages between networks |
US7843831B2 (en) | 2006-08-22 | 2010-11-30 | Embarq Holdings Company Llc | System and method for routing data on a packet network |
US8040811B2 (en) | 2006-08-22 | 2011-10-18 | Embarq Holdings Company, Llc | System and method for collecting and managing network performance information |
US8199653B2 (en) | 2006-08-22 | 2012-06-12 | Embarq Holdings Company, Llc | System and method for communicating network performance information over a packet network |
US8238253B2 (en) | 2006-08-22 | 2012-08-07 | Embarq Holdings Company, Llc | System and method for monitoring interlayer devices and optimizing network performance |
US7889660B2 (en) | 2006-08-22 | 2011-02-15 | Embarq Holdings Company, Llc | System and method for synchronizing counters on an asynchronous packet communications network |
US8619600B2 (en) | 2006-08-22 | 2013-12-31 | Centurylink Intellectual Property Llc | System and method for establishing calls over a call path having best path metrics |
US8223655B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for provisioning resources of a packet network based on collected network performance information |
US8194555B2 (en) | 2006-08-22 | 2012-06-05 | Embarq Holdings Company, Llc | System and method for using distributed network performance information tables to manage network communications |
US8576722B2 (en) | 2006-08-22 | 2013-11-05 | Centurylink Intellectual Property Llc | System and method for modifying connectivity fault management packets |
US8274905B2 (en) | 2006-08-22 | 2012-09-25 | Embarq Holdings Company, Llc | System and method for displaying a graph representative of network performance over a time period |
US8537695B2 (en) | 2006-08-22 | 2013-09-17 | Centurylink Intellectual Property Llc | System and method for establishing a call being received by a trunk on a packet network |
US7684332B2 (en) | 2006-08-22 | 2010-03-23 | Embarq Holdings Company, Llc | System and method for adjusting the window size of a TCP packet through network elements |
US9479341B2 (en) | 2006-08-22 | 2016-10-25 | Centurylink Intellectual Property Llc | System and method for initiating diagnostics on a packet network node |
US8064391B2 (en) | 2006-08-22 | 2011-11-22 | Embarq Holdings Company, Llc | System and method for monitoring and optimizing network performance to a wireless device |
US8307065B2 (en) | 2006-08-22 | 2012-11-06 | Centurylink Intellectual Property Llc | System and method for remotely controlling network operators |
US8223654B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | Application-specific integrated circuit for monitoring and optimizing interlayer network performance |
US8549405B2 (en) | 2006-08-22 | 2013-10-01 | Centurylink Intellectual Property Llc | System and method for displaying a graphical representation of a network to identify nodes and node segments on the network that are not operating normally |
US8224255B2 (en) | 2006-08-22 | 2012-07-17 | Embarq Holdings Company, Llc | System and method for managing radio frequency windows |
US8743703B2 (en) | 2006-08-22 | 2014-06-03 | Centurylink Intellectual Property Llc | System and method for tracking application resource usage |
US8125897B2 (en) | 2006-08-22 | 2012-02-28 | Embarq Holdings Company Lp | System and method for monitoring and optimizing network performance with user datagram protocol network performance information packets |
US7808918B2 (en) * | 2006-08-22 | 2010-10-05 | Embarq Holdings Company, Llc | System and method for dynamically shaping network traffic |
US8098579B2 (en) | 2006-08-22 | 2012-01-17 | Embarq Holdings Company, LP | System and method for adjusting the window size of a TCP packet through remote network elements |
US8228791B2 (en) | 2006-08-22 | 2012-07-24 | Embarq Holdings Company, Llc | System and method for routing communications between packet networks based on intercarrier agreements |
US8015294B2 (en) | 2006-08-22 | 2011-09-06 | Embarq Holdings Company, LP | Pin-hole firewall for communicating data packets on a packet network |
US7467067B2 (en) * | 2006-09-27 | 2008-12-16 | Integrien Corporation | Self-learning integrity management system and related methods |
US7707285B2 (en) * | 2006-09-27 | 2010-04-27 | Integrien Corporation | System and method for generating and using fingerprints for integrity management |
US8086710B2 (en) | 2006-10-30 | 2011-12-27 | Quest Software, Inc. | Identity migration apparatus and method |
US7895332B2 (en) | 2006-10-30 | 2011-02-22 | Quest Software, Inc. | Identity migration system apparatus and method |
US7676706B2 (en) * | 2006-11-03 | 2010-03-09 | Computer Associates Think, Inc. | Baselining backend component response time to determine application performance |
US7673191B2 (en) * | 2006-11-03 | 2010-03-02 | Computer Associates Think, Inc. | Baselining backend component error rate to determine application performance |
US8819215B2 (en) * | 2007-01-29 | 2014-08-26 | Nokia Corporation | System, methods, apparatuses and computer program products for providing step-ahead computing |
US8111692B2 (en) | 2007-05-31 | 2012-02-07 | Embarq Holdings Company Llc | System and method for modifying network traffic |
US8032867B2 (en) | 2007-06-05 | 2011-10-04 | Computer Associates Think, Inc. | Programmatic root cause analysis for application performance management |
US7783666B1 (en) | 2007-09-26 | 2010-08-24 | Netapp, Inc. | Controlling access to storage resources by using access pattern based quotas |
US8135824B2 (en) * | 2007-10-01 | 2012-03-13 | Ebay Inc. | Method and system to detect a network deficiency |
US8305896B2 (en) * | 2007-10-31 | 2012-11-06 | Cisco Technology, Inc. | Selective performance enhancement of traffic flows |
US8068425B2 (en) | 2008-04-09 | 2011-11-29 | Embarq Holdings Company, Llc | System and method for using network performance information to determine improved measures of path states |
WO2010000323A1 (en) * | 2008-07-03 | 2010-01-07 | Telefonaktiebolaget Lm Ericsson (Publ) | Management of performance data |
WO2010017205A2 (en) * | 2008-08-04 | 2010-02-11 | Jeffrey Harrang | Systems and methods for video bookmarking |
US8631117B2 (en) * | 2008-08-19 | 2014-01-14 | Vmware, Inc. | System and method for correlating fingerprints for automated intelligence |
US7969893B2 (en) * | 2008-08-22 | 2011-06-28 | Fluke Corporation | List-based alerting in traffic monitoring |
US9300993B2 (en) | 2008-08-29 | 2016-03-29 | Centurylink Intellectual Property Llc | Method and system for providing a content notification for a set-top box |
US20100088197A1 (en) * | 2008-10-02 | 2010-04-08 | Dehaan Michael Paul | Systems and methods for generating remote system inventory capable of differential update reports |
US9143341B2 (en) | 2008-11-07 | 2015-09-22 | Opanga Networks, Inc. | Systems and methods for portable data storage devices that automatically initiate data transfers utilizing host devices |
US8775574B2 (en) * | 2008-11-26 | 2014-07-08 | Red Hat, Inc. | Remote network management having multi-node awareness |
US8719392B2 (en) | 2009-02-27 | 2014-05-06 | Red Hat, Inc. | Searching a managed network for setting and configuration data |
US8078913B2 (en) * | 2009-05-28 | 2011-12-13 | Microsoft Corporation | Automated identification of performance crisis |
US8566459B2 (en) * | 2009-05-29 | 2013-10-22 | Red Hat, Inc. | Systems and methods for integrated console management interface |
US8467275B2 (en) | 2009-05-29 | 2013-06-18 | Centurylink Intellectual Property Llc | System and method for sharing user content through a set-top box |
US9280399B2 (en) * | 2009-05-29 | 2016-03-08 | Red Hat, Inc. | Detecting, monitoring, and configuring services in a netwowk |
CN101594622B (en) * | 2009-06-15 | 2011-06-08 | 上海华为技术有限公司 | Method, device and system for detecting dormant cell |
US8255984B1 (en) | 2009-07-01 | 2012-08-28 | Quest Software, Inc. | Single sign-on system for shared resource environments |
WO2011022096A1 (en) | 2009-08-19 | 2011-02-24 | Opanga Networks, Inc | Optimizing media content delivery based on user equipment determined resource metrics |
US8886790B2 (en) | 2009-08-19 | 2014-11-11 | Opanga Networks, Inc. | Systems and methods for optimizing channel resources by coordinating data transfers based on data type and traffic |
US7978711B2 (en) | 2009-08-20 | 2011-07-12 | Opanga Networks, Inc. | Systems and methods for broadcasting content using surplus network capacity |
US8166341B2 (en) * | 2009-08-31 | 2012-04-24 | Red Hat, Inc. | Systems and methods for testing results of configuration management activity |
US8914787B2 (en) * | 2009-08-31 | 2014-12-16 | Red Hat, Inc. | Registering software management component types in a managed network |
US8463885B2 (en) * | 2009-08-31 | 2013-06-11 | Red Hat, Inc. | Systems and methods for generating management agent installations |
US8032779B2 (en) * | 2009-08-31 | 2011-10-04 | Cisco Technology, Inc. | Adaptively collecting network event forensic data |
US8607093B2 (en) * | 2009-08-31 | 2013-12-10 | Red Hat, Inc. | Systems and methods for detecting machine faults in network using acoustic monitoring |
US9967169B2 (en) * | 2009-09-30 | 2018-05-08 | Red Hat, Inc. | Detecting network conditions based on correlation between trend lines |
JP5487864B2 (en) * | 2009-09-30 | 2014-05-14 | 富士通株式会社 | Data collection device, data collection method, and data collection program |
US20110098973A1 (en) * | 2009-10-23 | 2011-04-28 | Computer Associates Think, Inc. | Automatic Baselining Of Metrics For Application Performance Management |
US8719782B2 (en) | 2009-10-29 | 2014-05-06 | Red Hat, Inc. | Integrated package development and machine configuration management |
US8443107B2 (en) | 2009-11-11 | 2013-05-14 | Digital Envoy, Inc. | Method, computer program product and electronic device for hyper-local geo-targeting |
US20110161048A1 (en) * | 2009-12-31 | 2011-06-30 | Bmc Software, Inc. | Method to Optimize Prediction of Threshold Violations Using Baselines |
US8495196B2 (en) | 2010-03-22 | 2013-07-23 | Opanga Networks, Inc. | Systems and methods for aligning media content delivery sessions with historical network usage |
US8478569B2 (en) * | 2010-03-26 | 2013-07-02 | Bmc Software, Inc. | Auto adjustment of baseline on configuration change |
US8457928B2 (en) * | 2010-03-26 | 2013-06-04 | Bmc Software, Inc. | Automatic determination of dynamic threshold for accurate detection of abnormalities |
US9384112B2 (en) | 2010-07-01 | 2016-07-05 | Logrhythm, Inc. | Log collection, structuring and processing |
US8527811B2 (en) | 2010-09-13 | 2013-09-03 | International Business Machines Corporation | Problem record signature generation, classification and search in problem determination |
US9780995B2 (en) | 2010-11-24 | 2017-10-03 | Logrhythm, Inc. | Advanced intelligence engine |
CA2817576C (en) | 2010-11-24 | 2016-06-07 | Logrhythm, Inc. | Scalable analytical processing of structured data |
WO2012125478A1 (en) * | 2011-03-11 | 2012-09-20 | Interdigital Patent Holdings, Inc. | Method and apparatus for handling bursty network entry and re-entry in machine to machine networks |
US8689055B2 (en) * | 2011-07-28 | 2014-04-01 | International Business Machines Corporation | Detecting device impairment through statistical monitoring |
CN104322093A (en) * | 2012-05-22 | 2015-01-28 | 爱立信(中国)通信有限公司 | Method and apparatus for detecting a sleeping cell |
US9973397B2 (en) * | 2014-07-23 | 2018-05-15 | Guavus, Inc. | Diagnosis of network anomalies using customer probes |
US9450916B2 (en) | 2014-08-22 | 2016-09-20 | Honeywell International Inc. | Hardware assist for redundant ethernet network |
US10291487B2 (en) | 2016-06-08 | 2019-05-14 | Bank Of America Corporation | System for predictive acquisition and use of resources |
US10129126B2 (en) * | 2016-06-08 | 2018-11-13 | Bank Of America Corporation | System for predictive usage of resources |
US10178101B2 (en) | 2016-06-08 | 2019-01-08 | Bank Of America Corporation | System for creation of alternative path to resource acquisition |
US10581988B2 (en) | 2016-06-08 | 2020-03-03 | Bank Of America Corporation | System for predictive use of resources |
US11558271B2 (en) * | 2019-09-04 | 2023-01-17 | Cisco Technology, Inc. | System and method of comparing time periods before and after a network temporal event |
Family Cites Families (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5235166A (en) * | 1991-02-14 | 1993-08-10 | Xtec Incorporated | Data verification method and magnetic media therefor |
US5586254A (en) * | 1992-02-13 | 1996-12-17 | Hitachi Software Engineering Co., Ltd. | System for managing and operating a network by physically imaging the network |
US5819028A (en) * | 1992-06-10 | 1998-10-06 | Bay Networks, Inc. | Method and apparatus for determining the health of a network |
US5450406A (en) * | 1993-04-20 | 1995-09-12 | Kabushiki Kaisha Toshiba | ATM communication system with high speed connection-less service function |
US5513126A (en) * | 1993-10-04 | 1996-04-30 | Xerox Corporation | Network having selectively accessible recipient prioritized communication channel profiles |
US5974457A (en) * | 1993-12-23 | 1999-10-26 | International Business Machines Corporation | Intelligent realtime monitoring of data traffic |
US5619656A (en) * | 1994-05-05 | 1997-04-08 | Openservice, Inc. | System for uninterruptively displaying only relevant and non-redundant alert message of the highest severity for specific condition associated with group of computers being managed |
US5491791A (en) * | 1995-01-13 | 1996-02-13 | International Business Machines Corporation | System and method for remote workstation monitoring within a distributed computing environment |
US5696486A (en) * | 1995-03-29 | 1997-12-09 | Cabletron Systems, Inc. | Method and apparatus for policy-based alarm notification in a distributed network management environment |
US5699403A (en) * | 1995-04-12 | 1997-12-16 | Lucent Technologies Inc. | Network vulnerability management apparatus and method |
US5752062A (en) * | 1995-10-02 | 1998-05-12 | International Business Machines Corporation | Method and system for performance monitoring through monitoring an order of processor events during execution in a processing system |
US5799154A (en) * | 1996-06-27 | 1998-08-25 | Mci Communications Corporation | System and method for the remote monitoring of wireless packet data networks |
US5850388A (en) * | 1996-08-02 | 1998-12-15 | Wandel & Goltermann Technologies, Inc. | Protocol analyzer for monitoring digital transmission networks |
US5991881A (en) * | 1996-11-08 | 1999-11-23 | Harris Corporation | Network surveillance system |
US5974237A (en) * | 1996-12-18 | 1999-10-26 | Northern Telecom Limited | Communications network monitoring |
-
1998
- 1998-04-27 US US09/067,319 patent/US6327677B1/en not_active Expired - Lifetime
- 1998-04-27 US US09/067,319 patent/US20010052087A1/en active Granted
Cited By (80)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6591377B1 (en) * | 1999-11-24 | 2003-07-08 | Unisys Corporation | Method for comparing system states at different points in time |
US20020053018A1 (en) * | 2000-06-12 | 2002-05-02 | Kenji Ota | Apparatus and method to identify computer system |
US20020107958A1 (en) * | 2000-10-31 | 2002-08-08 | Faraldo David D. | Method of and apparatus for notification of state changes in a monitored system |
US8145742B1 (en) | 2000-10-31 | 2012-03-27 | Red Hat, Inc. | Method of and apparatus for network administration |
US8219663B2 (en) * | 2000-10-31 | 2012-07-10 | Red Hat, Inc. | Method of and apparatus for notification of state changes in a monitored system |
US6950868B1 (en) * | 2000-10-31 | 2005-09-27 | Red Hat, Inc. | Method of and apparatus for remote monitoring |
US20070005761A1 (en) * | 2001-04-07 | 2007-01-04 | Webmethods, Inc. | Predictive monitoring and problem identification in an information technology (it) infrastructure |
US7107339B1 (en) * | 2001-04-07 | 2006-09-12 | Webmethods, Inc. | Predictive monitoring and problem identification in an information technology (IT) infrastructure |
US20030172152A1 (en) * | 2002-03-11 | 2003-09-11 | Qwest Communications International Inc. | Automated module tracking system for communications networks |
US20030172153A1 (en) * | 2002-03-11 | 2003-09-11 | Qwest Communications International Inc. | Systems and methods for tracking the reliability of communications networks |
US7523192B2 (en) * | 2002-03-11 | 2009-04-21 | Qwest Communications International Inc. | Automated module tracking system for communications networks |
US8549133B2 (en) | 2002-03-11 | 2013-10-01 | Qwest Communications International Inc. | Systems and methods for tracking the reliability of communications networks |
US20080133749A1 (en) * | 2002-11-08 | 2008-06-05 | Federal Network Systems, Llc | Server resource management, analysis, and intrusion negation |
US8763119B2 (en) | 2002-11-08 | 2014-06-24 | Home Run Patents Llc | Server resource management, analysis, and intrusion negotiation |
US8397296B2 (en) * | 2002-11-08 | 2013-03-12 | Verizon Patent And Licensing Inc. | Server resource management, analysis, and intrusion negation |
US20140365643A1 (en) * | 2002-11-08 | 2014-12-11 | Palo Alto Networks, Inc. | Server resource management, analysis, and intrusion negotiation |
US20080222727A1 (en) * | 2002-11-08 | 2008-09-11 | Federal Network Systems, Llc | Systems and methods for preventing intrusion at a web host |
US8001239B2 (en) | 2002-11-08 | 2011-08-16 | Verizon Patent And Licensing Inc. | Systems and methods for preventing intrusion at a web host |
US9391863B2 (en) * | 2002-11-08 | 2016-07-12 | Palo Alto Networks, Inc. | Server resource management, analysis, and intrusion negotiation |
US20040103185A1 (en) * | 2002-11-21 | 2004-05-27 | Combs Nathan Hideaki | Adaptive self-repair and configuration in distributed systems |
US20040193956A1 (en) * | 2003-03-28 | 2004-09-30 | International Business Machines Corporation | System, method and program product for checking a health of a computer system |
US8024608B2 (en) | 2003-03-28 | 2011-09-20 | International Business Machines Corporation | Solution for checking a health of a computer system |
US7392430B2 (en) * | 2003-03-28 | 2008-06-24 | International Business Machines Corporation | System and program product for checking a health of a computer system |
US20080155558A1 (en) * | 2003-03-28 | 2008-06-26 | Gordan Greenlee | Solution for checking a health of a computer system |
US20080216098A1 (en) * | 2003-10-20 | 2008-09-04 | International Business Machines Corporation | Systems, methods and computer porograms for determining dependencies between logical components in a data processing system or network |
US7409676B2 (en) | 2003-10-20 | 2008-08-05 | International Business Machines Corporation | Systems, methods and computer programs for determining dependencies between logical components in a data processing system or network |
US8132180B2 (en) | 2003-10-20 | 2012-03-06 | International Business Machines Corporation | Systems, methods and computer programs for determining dependencies between logical components in a data processing system or network |
US20080189717A1 (en) * | 2003-10-20 | 2008-08-07 | International Business Machines Corporation | Systems, methods and computer programs for determining dependencies between logical components in a data processing system or network |
US8006230B2 (en) | 2003-10-20 | 2011-08-23 | International Business Machines Corporation | Systems, methods and computer programs for determining dependencies between logical components in a data processing system or network |
US20050172306A1 (en) * | 2003-10-20 | 2005-08-04 | Agarwal Manoj K. | Systems, methods and computer programs for determining dependencies between logical components in a data processing system or network |
US7457722B1 (en) | 2004-11-17 | 2008-11-25 | Symantec Operating Corporation | Correlation of application instance life cycle events in performance monitoring |
US7250855B2 (en) * | 2004-12-27 | 2007-07-31 | Sap Aktiengesellschaft | False alarm mitigation using a sensor network |
US20060152355A1 (en) * | 2004-12-27 | 2006-07-13 | Asuman Suenbuel | False alarm mitigation using a sensor network |
US8438264B2 (en) | 2004-12-28 | 2013-05-07 | At&T Intellectual Property I, L.P. | Method and apparatus for collecting, analyzing, and presenting data in a communication network |
US20060142001A1 (en) * | 2004-12-28 | 2006-06-29 | Moisan Kevin J | Methods and apparatus for monitoring a communication network |
US9231837B2 (en) | 2004-12-28 | 2016-01-05 | At&T Intellectual Property I, L.P. | Methods and apparatus for collecting, analyzing, and presenting data in a communication network |
US7877634B2 (en) * | 2005-04-20 | 2011-01-25 | Mitsubishi Electric Corp. | Data collecting apparatus and gateway apparatus |
US20090013220A1 (en) * | 2005-04-20 | 2009-01-08 | Mitsubishi Electric Corporation | Data Collecting Apparatus and Gateway Apparatus |
US7630327B2 (en) * | 2005-07-13 | 2009-12-08 | Andrew Llc | Method for data maintenance and integration including interpolation |
US20070165541A1 (en) * | 2005-07-13 | 2007-07-19 | John Arpee | System and method for data maintenance and integration including interpolation |
US20070019548A1 (en) * | 2005-07-22 | 2007-01-25 | Balachander Krishnamurthy | Method and apparatus for data network sampling |
US20070064736A1 (en) * | 2005-09-19 | 2007-03-22 | Fujitsu Network Communications | Zero suppressed performance management data interpretation and same value suppression and interpretation |
US20070297001A1 (en) * | 2006-06-22 | 2007-12-27 | Brian Podl | Multi-function peripheral remote alert notification system and method |
US8238258B2 (en) * | 2006-12-08 | 2012-08-07 | At&T Intellectual Property I, L.P. | System and method of managing network performance |
US20080137549A1 (en) * | 2006-12-08 | 2008-06-12 | At&T Knowledge Ventures, Lp | System and method of managing network performance |
US7904457B2 (en) | 2007-05-30 | 2011-03-08 | International Business Machines Corporation | Semantic correlation for flow analysis in messaging systems |
US8451731B1 (en) | 2007-07-25 | 2013-05-28 | Xangati, Inc. | Network monitoring using virtual packets |
US8639797B1 (en) * | 2007-08-03 | 2014-01-28 | Xangati, Inc. | Network monitoring of behavior probability density |
US8224942B1 (en) * | 2007-10-02 | 2012-07-17 | Google Inc. | Network failure detection |
US8745195B1 (en) | 2007-10-02 | 2014-06-03 | Google Inc. | Network failure detection |
US9106518B1 (en) | 2007-10-02 | 2015-08-11 | Google Inc. | Network failure detection |
US10992555B2 (en) | 2009-05-29 | 2021-04-27 | Virtual Instruments Worldwide, Inc. | Recording, replay, and sharing of live network monitoring views |
US8942137B2 (en) * | 2009-07-14 | 2015-01-27 | Telefonaktiebolaget L M Ericsson (Publ) | Method and arrangement in a telecommunication system |
US20120113814A1 (en) * | 2009-07-14 | 2012-05-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Method And Arrangement In A Telecommunication System |
US20110153788A1 (en) * | 2009-12-23 | 2011-06-23 | Jacobus Van Der Merwe | Method and System for Automated Network Operations |
US9262370B2 (en) | 2010-02-01 | 2016-02-16 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US9959244B2 (en) * | 2010-02-01 | 2018-05-01 | Netmotion Wireless Holdings, Inc. | Public wireless network performance management system with mobile device data collection agents |
US11917408B2 (en) * | 2010-02-01 | 2024-02-27 | Mobile Sonic, Inc. | Public wireless network performance management system with mobile device data collection agents |
US20120284399A1 (en) * | 2010-02-01 | 2012-11-08 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US10198398B2 (en) | 2010-02-01 | 2019-02-05 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US9990331B2 (en) | 2010-02-01 | 2018-06-05 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US9971732B2 (en) * | 2010-02-01 | 2018-05-15 | Netmotion Wireless Holdings, Inc. | Public wireless network performance management system with mobile device data collection agents |
US20120282933A1 (en) * | 2010-02-01 | 2012-11-08 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US20120284376A1 (en) * | 2010-02-01 | 2012-11-08 | Netmotion Wireless, Inc. | Public wireless network performance management system with mobile device data collection agents |
US9965440B2 (en) | 2010-02-01 | 2018-05-08 | Netmotion Wireless Holdings, Inc. | Public wireless network performance management system with mobile device data collection agents |
US20120079325A1 (en) * | 2010-09-29 | 2012-03-29 | Sepaton, Inc. | System Health Monitor |
US8572434B2 (en) * | 2010-09-29 | 2013-10-29 | Sepaton, Inc. | System health monitor |
US8601578B1 (en) * | 2011-01-20 | 2013-12-03 | Google Inc. | Identifying potentially suspicious business listings for moderation |
US9158847B1 (en) * | 2011-07-19 | 2015-10-13 | Kyndi Inc. | Cognitive memory encoding networks for fast semantic indexing storage and retrieval |
US8600915B2 (en) | 2011-12-19 | 2013-12-03 | Go Daddy Operating Company, LLC | Systems for monitoring computer resources |
US8719196B2 (en) | 2011-12-19 | 2014-05-06 | Go Daddy Operating Company, LLC | Methods for monitoring computer resources using a first and second matrix, and a feature relationship tree |
GB2523629A (en) * | 2013-12-19 | 2015-09-02 | Bae Systems Plc | Network faul detection and location |
US10009263B1 (en) | 2015-10-09 | 2018-06-26 | Gigamon Inc. | Network switch device for routing network traffic through an inline tool |
US10785152B2 (en) | 2015-10-09 | 2020-09-22 | Gigamon Inc. | Network switch device for routing network traffic through an inline tool |
US9912575B2 (en) * | 2015-11-18 | 2018-03-06 | Gigamon Inc. | Routing network traffic packets through a shared inline tool |
US20170141996A1 (en) * | 2015-11-18 | 2017-05-18 | Gigamon Inc. | Routing network traffic packets through a shared inline tool |
CN107862866A (en) * | 2017-11-06 | 2018-03-30 | 浙江工商大学 | Noise data point detecting method based on the translation of mean deviation amount |
CN109688188A (en) * | 2018-09-07 | 2019-04-26 | 平安科技(深圳)有限公司 | Monitoring alarm method, apparatus, equipment and computer readable storage medium |
EP3905591A4 (en) * | 2018-12-29 | 2022-02-16 | Wangsu Science & Technology Co., Ltd. | Server abnormality processing method and management device |
US11449407B2 (en) | 2020-05-28 | 2022-09-20 | Bank Of America Corporation | System and method for monitoring computing platform parameters and dynamically generating and deploying monitoring packages |
Also Published As
Publication number | Publication date |
---|---|
US6327677B1 (en) | 2001-12-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6327677B1 (en) | Method and apparatus for monitoring a network environment | |
US6453346B1 (en) | Method and apparatus for intelligent storage and reduction of network information | |
US7574502B2 (en) | Early warning of potential service level agreement violations | |
US7877472B2 (en) | System and method for displaying historical performance of an element on a network | |
US6966015B2 (en) | Method and system for reducing false alarms in network fault management systems | |
US6658367B2 (en) | System for time-bucketing of baselined data collector data | |
US7500142B1 (en) | Preliminary classification of events to facilitate cause-based analysis | |
US5974457A (en) | Intelligent realtime monitoring of data traffic | |
US6986076B1 (en) | Proactive method for ensuring availability in a clustered system | |
US8700761B2 (en) | Method and system for detecting and managing a fault alarm storm | |
US5796633A (en) | Method and system for performance monitoring in computer networks | |
US6816898B1 (en) | Interfacing external metrics into a performance management system | |
US6941367B2 (en) | System for monitoring relevant events by comparing message relation key | |
Lim et al. | A log mining approach to failure analysis of enterprise telephony systems | |
US20030115508A1 (en) | System and method for collecting statistics for a communication network | |
AU2001270017A1 (en) | Liveexception system | |
US6633834B2 (en) | Baselining of data collector data | |
EP2332078A1 (en) | Log file time sequence stamping | |
US7469287B1 (en) | Apparatus and method for monitoring objects in a network and automatically validating events relating to the objects | |
CA2726766C (en) | Using metadata analysis for monitoring, alerting, and remediation | |
CN114095522A (en) | Vehicle monitoring method, service system, management terminal, vehicle and storage medium | |
US7673035B2 (en) | Apparatus and method for processing data relating to events on a network | |
US20230216771A1 (en) | Algorithm for building in-context report dashboards | |
Song et al. | Internet router outage measurement: An embedded approach | |
CN117411801A (en) | Aviation Internet all-link monitoring and alarming system based on grafana |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:BMC SOFTWARE, INC.;BLADELOGIC, INC.;REEL/FRAME:031204/0225 Effective date: 20130910 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY AGREEMENT;ASSIGNORS:BMC SOFTWARE, INC.;BLADELOGIC, INC.;REEL/FRAME:031204/0225 Effective date: 20130910 |
|
AS | Assignment |
Owner name: CREDIT SUISSE, AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NEW YORK Free format text: SECURITY INTEREST;ASSIGNORS:BMC SOFTWARE, INC.;BLADELOGIC, INC.;REEL/FRAME:047185/0744 Effective date: 20181002 Owner name: CREDIT SUISSE, AG, CAYMAN ISLANDS BRANCH, AS COLLA Free format text: SECURITY INTEREST;ASSIGNORS:BMC SOFTWARE, INC.;BLADELOGIC, INC.;REEL/FRAME:047185/0744 Effective date: 20181002 |
|
AS | Assignment |
Owner name: BLADELOGIC, INC., TEXAS Free format text: RELEASE OF PATENTS;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:047198/0468 Effective date: 20181002 Owner name: BMC ACQUISITION L.L.C., TEXAS Free format text: RELEASE OF PATENTS;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:047198/0468 Effective date: 20181002 Owner name: BMC SOFTWARE, INC., TEXAS Free format text: RELEASE OF PATENTS;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:047198/0468 Effective date: 20181002 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT, TEXAS Free format text: SECURITY INTEREST;ASSIGNORS:BMC SOFTWARE, INC.;BLADELOGIC, INC.;REEL/FRAME:052844/0646 Effective date: 20200601 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT, TEXAS Free format text: SECURITY INTEREST;ASSIGNORS:BMC SOFTWARE, INC.;BLADELOGIC, INC.;REEL/FRAME:052854/0139 Effective date: 20200601 |
|
AS | Assignment |
Owner name: ALTER DOMUS (US) LLC, ILLINOIS Free format text: GRANT OF SECOND LIEN SECURITY INTEREST IN PATENT RIGHTS;ASSIGNORS:BMC SOFTWARE, INC.;BLADELOGIC, INC.;REEL/FRAME:057683/0582 Effective date: 20210930 |
|
AS | Assignment |
Owner name: BLADELOGIC, INC., TEXAS Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:ALTER DOMUS (US) LLC;REEL/FRAME:066567/0283 Effective date: 20240131 Owner name: BMC SOFTWARE, INC., TEXAS Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:ALTER DOMUS (US) LLC;REEL/FRAME:066567/0283 Effective date: 20240131 |
|
AS | Assignment |
Owner name: GOLDMAN SACHS BANK USA, AS SUCCESSOR COLLATERAL AGENT, NEW YORK Free format text: OMNIBUS ASSIGNMENT OF SECURITY INTERESTS IN PATENT COLLATERAL;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS RESIGNING COLLATERAL AGENT;REEL/FRAME:066729/0889 Effective date: 20240229 |