WO2004001555A2 - Method and system for monitoring performance of application in a distributed environment - Google Patents

Method and system for monitoring performance of application in a distributed environment Download PDF

Info

Publication number
WO2004001555A2
WO2004001555A2 PCT/US2003/020109 US0320109W WO2004001555A2 WO 2004001555 A2 WO2004001555 A2 WO 2004001555A2 US 0320109 W US0320109 W US 0320109W WO 2004001555 A2 WO2004001555 A2 WO 2004001555A2
Authority
WO
WIPO (PCT)
Prior art keywords
user
server
performance
monitoring
request
Prior art date
Application number
PCT/US2003/020109
Other languages
French (fr)
Other versions
WO2004001555A3 (en
Inventor
James C. Chong
Joseph L. Chan
Tushar M. Patel
Jean-Jacques Heler
Chi Hong So
Arthur Tsang
Robert S. Lam
Raymond Chow
Henry Tang
Jerome D. Banks
Christopher M. Zychowski
Original Assignee
International Business Machines Corporation
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by International Business Machines Corporation filed Critical International Business Machines Corporation
Priority to EP03742215A priority Critical patent/EP1527395A4/en
Priority to JP2004516267A priority patent/JP4528116B2/en
Priority to AU2003278862A priority patent/AU2003278862A1/en
Publication of WO2004001555A2 publication Critical patent/WO2004001555A2/en
Publication of WO2004001555A3 publication Critical patent/WO2004001555A3/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3006Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/16Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/11File system administration, e.g. details of archiving or snapshots
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3065Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • G06F11/3072Monitoring arrangements determined by the means or processing involved in reporting the monitored data where the reporting involves data filtering, e.g. pattern matching, time or event triggered, adaptive or policy-based reporting
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/32Monitoring with visual or acoustical indication of the functioning of the machine
    • G06F11/324Display of status information
    • G06F11/328Computer systems status display
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3409Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466Performance evaluation by tracing or monitoring
    • G06F11/3476Data logging
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/34Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
    • G06F11/3466Performance evaluation by tracing or monitoring
    • G06F11/3495Performance evaluation by tracing or monitoring for systems
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00Digital computers in general; Data processing equipment in general
    • G06F15/16Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • G06F15/163Interprocessor communication
    • G06F15/173Interprocessor communication using an interconnection network, e.g. matrix, shuffle, pyramid, star, snowflake
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/81Threshold
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/865Monitoring of software
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/88Monitoring involving counting

Definitions

  • This invention relates to computer software, and in particular to distributed computing.
  • a method in accordance with the invention for monitoring the performance of applications running on a server in a distributed computing environment comprises the step of prompting the user to select information for monitoring, monitoring application performance in accordance with the selected information, and making the monitored performance information available to the user.
  • a method in accordance with the invention includes the steps of prompting a user to select a server or server group, a resource, and a threshold or condition for notification, comparing the value or quality of the parameter to the threshold or condition, and providing a notification to the user in the event that the parameter reaches the threshold or condition.
  • a method according to the invention comprises the steps of providing the user with performance information relating to applications running on a server in a distributed computing environment, receiving from the user a request for more specific performance information, and providing more detailed performance information in response to the request.
  • a method according to the invention includes the steps of receiving from the user an identification of a server as an authoritative server, another server as a comparison server, comparing runtime environment data in the form of one or more of CPU data, server data and Java data between the selected servers, and displaying differences to a user.
  • a method of the invention includes the steps of receiving from the user an identification of a server as an authoritative server, and another server as a comparison server, and providing a list of matching and differing file names.
  • the method may further include the step of receiving from the user a selection of a file, conducting a comparison of the files, and providing a result to the user.
  • a method of the invention includes the steps of receiving a request string, and mapping the received request string to a distinguishable request string and a collapsible request string.
  • the received request string may be in the form of a JSP, a servlet, and remote Enterprise Java Bean calls.
  • a method of the invention may prompt a user to create rules for mapping of a received request string to a distinguishable request string and a collapsible request string.
  • a method of the invention includes the steps of providing, in a system running at least one application, a management application having various components for monitoring and management, and monitoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components.
  • a method of the invention includes the steps of assigning a role to each user, and mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user.
  • a system in accordance with the invention for monitoring the performance of applications running on a server in a distributed computing environment includes computer hardware and software for prompting the user to select information for monitoring, computer hardware and software for monitoring application performance in accordance with the selected information received from the user, and computer hardware and software for making the monitored performance information available to the user.
  • a system in accordance with the invention includes computer hardware and software for prompting a user to select a server or server group, a resource, and a threshold or condition for notification, computer software and hardware for comparing a value or quality of a monitored parameter of the resource on the server or server group to the threshold or condition, and computer software and hardware for providing a notification to the user in the event that the parameter reaches the threshold or condition.
  • a system includes computer hardware and software for providing the user with performance information relating to one or more applications running on a server in a distributed computing environment, computer hardware and software for receiving from the user a request for more specific performance information, and computer hardware and software for providing more detailed performance information in response to the request.
  • a system includes computer hardware and software for receiving from a user an identification of a first server as an authoritative server and a second server as a comparison server, computer hardware and software for comparing runtime environment data from the authoritative server and the comparison server in the form of one or more of CPU data, server data and Java data between the selected servers, and computer hardware and software for displaying differences in such data between the selected servers to a user.
  • a system includes computer hardware and software for receiving from the user an identification of a first server as an authoritative server and a second server as a comparison server, and computer hardware and software for providing a list of matching and differing file names.
  • the system may further include computer hardware for receiving from the user a selection of a file on both the authoritative server and the comparison server, computer hardware and software for conducting a comparison of the files, and for providing a result to the user.
  • a system of the invention includes computer hardware and software for receiving a request string, and computer hardware and software for mapping the received request string to a distinguishable request string and a collapsible request string.
  • the received request string may be in the form of a JSP, a servlet, and remote Enterprise Java Bean calls.
  • a system of the invention may include computer hardware and software for prompting a user to create rules for mapping of a received request string to a distinguishable request string and a collapsible request string.
  • a system of the invention includes computer hardware and software for providing, in a system running at least one application, a management application having various components for monitoring and management, and for monitoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components.
  • a system of the invention includes computer hardware and software for assigning a role to each user, and computer hardware and software for mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user.
  • a computer program in accordance with the invention for monitoring the performance of applications running on a server in a distributed computing environment consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of prompting the user to select information for monitoring, monitoring application performance in accordance with the selected information, and making the monitored performance information available to the user.
  • a computer program in accordance with the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of prompting a user to select a server or server group, a resource, and a threshold or condition for notification, comparing a detected value or quality of a parameter of the resource on the server or server group to the threshold or condition, and providing a notification to the user in the event that the parameter reaches the threshold or condition.
  • a computer program according to the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of providing the user with performance information relating to applications running on a server in a distributed computing environment, receiving from the user a request for more specific performance information, and providing more detailed performance information in response to the request.
  • a computer program according to the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of receiving from the user an identification of a first server as an authoritative server, a second server as a comparison server, comparing runtime environment data in the form of one or more of CPU data, server data and Java data between the selected servers, and displaying differences to a user.
  • a computer program consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of receiving from a user an identification of a first server as an authoritative server, and a second server as a comparison server, and providing a list of matching and differing file names between the first and second servers.
  • the program may further include instructions which, when executed on a processor, cause the processor to execute the steps of receiving from the user a selection of a file found on both the first and second servers, conducting a comparison of the files, and providing a result to the user.
  • a computer program of the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of receiving a request string, and mapping the received request string to a distinguishable request string and a collapsible request string.
  • the received request string may be in the form of a JSP, a servlet, and remote Enterprise Java Bean calls.
  • a computer program of the invention consists of instructions stored on a medium, which instructions, when executed on a processor, causing the processor to execute the steps of providing, in a system running at least one application, a management application having various components for monitoring and management, and monitoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components.
  • a computer program of the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of assigning a role to each user, and mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user.
  • FIG. 2A and 2B is a flow diagram illustrating a method in accordance with the invention.
  • FIG. 3 is a schematic illustration of a method in accordance with the invention.
  • Fig. 4 is a flow diagram illustrating a method in accordance with the invention.
  • FIG. 5 is a flow diagram illustrating a method in accordance with the invention.
  • Fig. 6 is a schematic diagram illustrating a feature of the invention.
  • Fig. 7 is a schematic diagram illustrating a feature of the invention.
  • Fig. 8 is a schematic diagram illustrating an exemplary architecture.
  • Fig. 9 is a schematic diagram illustrating features of an exemplary architecture.
  • Fig. 10 is a diagram illustrating features of an exemplary architecture.
  • Fig. 11 is a schematic diagram illustrating features of an exemplary architecture.
  • Fig. 12 is a schematic diagram illustrating features of an exemplary architecture.
  • Fig. 13 is flow diagram illustrating an exemplary architecture.
  • the invention includes a process for monitoring and providing information about the performance of certain aspects of computer systems, and computer programs and systems for accomplishing these purposes. The method and system will be described with reference to a computer program for accomplishing these purposes and for use in a system of the invention.
  • the computer program of the invention is particularly useful for applications running on application servers.
  • the computer program of the invention includes a user interface providing a variety of information and options to the user. Probes installed on application servers obtain information related to the operation of the applications and servers and furnish that information to other program elements for analysis and reporting to the user. Monitoring Levels and Schedule
  • a capability for providing selected levels of detail about the operation of applications running on a server A user is prompted to identify information for monitoring, as indicated in Fig. 1 at 105.
  • a user is preferably provided with at least two choices as to the level of detail of monitoring.
  • the term level of detail of monitoring refers to the amount and nature of information that is obtained about the running of the applications.
  • the level of detail of monitoring may refer to the amount of data or information that is being obtained.
  • the level of detail may also refer to the nature of the information that is being obtained. For example, some types of information, such as server availability information, are at a relatively high level of detail. Other types of information, such as method trace information, are at a relatively low level of detail.
  • the user may be prompted to select a level of monitoring.
  • the user may select particular features to monitor.
  • preselected monitoring levels may be provided. Each preselected monitoring level has associated therewith particular information that is monitored and reported.
  • the program of the invention monitors application performance, as indicated, and makes the monitored performance information available to the user. In one example, illustrated in Fig. 1, three levels of monitoring may be provided.
  • the system determines the monitoring level, as indicated by decision block 115. At Level 1, the highest level, and therefore the level providing the least information, the information may be in the nature of request level data and server level data.
  • the associated information may be availability management, system resources and distributed platforms, and basic request data, as indicated at block 120.
  • Availability management includes information as to whether a particular application is running on a particular server.
  • System resources indicates such information as the amount of available memory and number of available connections.
  • Basic request data indicates the number of requests being made, the number of requests being completed, and the like.
  • Level 2 monitoring may be provided with a selection of Level 2 monitoring.
  • a Level 2 monitoring selection ordinarily include all of the information provided by Level 1 monitoring, with additional information, as indicated at block 125.
  • the additional information may be API level data, such as SQL data, JMS data and EJB call data. Such data may include data regarding the throughput of a particular CPU.
  • the functionality to permit the user to provide a soft cancel of a request may be provided.
  • No method data or SQL level data is provided.
  • the JVMPI is enabled on the corresponding JVMs. This level is directed at problem determination, and may be used for servers with a high volume of transactions, with occasional instability. The complexity of the transactions may vary. Because the JVMPI is enabled on the corresponding JVM, the user may be provided with the option of changing dynamically to a more detailed level of monitoring, such as Level 3 described below.
  • Level 3 monitoring provides the information furnished in connection with Level 2 monitoring, plus method level data.
  • Level 3 may include advanced problem determination and reporting, including, for example, method and SQL level data, as indicated by block 130.
  • the JVMPI is enabled on the corresponding JVMs. JVMPI function calls are possible, and method entry and exit events are selected. This level is typically used for servers which have been selected for diagnostics, detailed workload characterization and profiling. Since this level requires enabling of the JVMPI, as noted above, it is possible to dynamically change between this level and other levels in which the JVMPI has been enabled, such as the exemplary Level 2 described above. In all cases, as noted above, and as indicated by block 135, monitored information is presented to the user.
  • the user is prompted to define a schedule for monitoring, as indicated by block 140.
  • the schedule is received from the user, as indicated by block 145, and monitoring proceeds in accordance with the schedule as indicated by block 150.
  • a schedule defines at least a start time, preferably defined by calendar date and time, a monitoring level, and a server or group of servers. Rather than a monitoring level, the program of the invention could permit the user to select individual data items for monitoring.
  • the schedule may define times for the monitoring level to change, which may also be in terms of a calendar date and time.
  • the schedule may be selected to cycle on an appropriate basis, such as each month, each week, or each day.
  • a schedule consists of a group of schedule records, each of which is a combination of a start date and time and a monitoring level.
  • the program of the invention causes monitoring to commence with the first schedule record, and monitoring to change when the current time is the start time and date of another schedule record. This process continues through successive schedule records.
  • a default monitoring level may be provided for use at a time when no monitoring is specified in the schedule.
  • the program may be furnished with a default, which may be changed by the user.
  • the user is prompted to apply a completed schedule to one or more servers or server groups.
  • the user may be provided the option to duplicate an existing schedule, and then be prompted for servers and server groups to which to apply the schedule.
  • the user may be provided the option of modifying the fields of a schedule.
  • a schedule is modified by removal of a server or server group, the user will be prompted to apply another schedule to that server or server group.
  • the program may be configured to prevent the user from removing all schedules from a given server.
  • monitoring of the affected server or server groups may return to a default monitoring level.
  • the user may be provided the option of deleting a schedule, and monitoring may take place at a default level for the time and server or server groups corresponding to the deleted schedule.
  • a system of the invention may permit a user with proper authorization to manually change the items to be monitored. Such a manual change would preferably only be available on a temporary basis, and may be limited to a particular server or server group.
  • the system follows a hierarchical search path to determine the proper level of monitoring. If it is possible to contact the scheduler, ask for a temporary override, and then a scheduled monitoring level, then the system- wide monitoring level is used. When the scheduler cannot be contacted, then the default monitoring level is used. Monitoring Traps and Alerts
  • alerts are provided to the user. Alerts are provided as a result of a parameter of a monitored resource on a selected server or server group reaching a selected matching condition or threshold value for that condition.
  • the software that is capable of providing a notification or alert to the user is referred to here as a software trap.
  • the user may select the option of creating or modifying a software trap from a menu in a program according to the invention. There are a number of selections which a user is prompted to make in order to create a new software trap. These selections include the servers or server groups on which the trap will be applied, the resource to be measured, and the condition.
  • the first step may be to prompt the user to select a server or server group, as indicated at block 205. The selection is received, as indicated by block 210.
  • a resource and a condition in the form of a threshold value must be selected.
  • Resources may include occurrence, CPU time, resident time, wait time, and SQL resident time. Threshold values would depend on the particular type of resource.
  • the system may provide the units to the user for selection of the threshold value.
  • the trap can be applied to any request, to a specific request name, or to a specific method name.
  • the trap then proceeds to monitor the selected resource, as indicated by block 235. If a threshold is met, then the system evaluates whether an alert condition has been triggered, as indicated at blocks 236 and 237.
  • a resource and condition with a number of hits must be selected.
  • the resource may be, for example, an HTTP request parameter, or an SQL statements.
  • a condition is a specified string contained in the HTTP/SPL request.
  • the condition may also be in the form of a Boolean expression applied to strings.
  • the software trap When the user provides the requested resource and condition, at 244, the software trap performs monitoring, as at 246 of Fig. 2B. Whenever a request or statement is identified meeting the condition, a hit counter is incremented, as indicated by blocks 248, 250 and 252 in Fig. 2B. If sufficient hits are counted, then an alert condition is reached, and an alert is communicated and recorded, as at 254.
  • a third type of trap applies to the condition of the resource consumption of the application server.
  • the user is required to select an application server or group.
  • the user is prompted to specify, for resource and threshold values, a resource, and a threshold, as indicated by blocks 260, 262 and 264 in Fig. 2B.
  • the resources may include information relating to application server availability, database connection pools, and JVM runtime memory. Server availability is measured as a simple positive or negative.
  • database connection pools a number of different thresholds may be set, including: number of connections allocated to number of connections; average number of threads waiting for a connection; average time that a client waits to be granted a connection; number of connection pool timeouts; and average percent of the pool in use.
  • resources may be the amount of free memory in the JVM runtime and the amount of memory used in the JVM runtime.
  • the user is prompted to provide a number and to indicate whether that number is a maximum or minimum. Suitable units may be provided to the user, e.g., Mbytes for free memory and memory used.
  • the user is also prompted to select the number of times that a condition is met before an alert message is created.
  • the resource is momtored, as indicated at 266, and if an alert condition is met, an alert is communicated and recorded, as shown at 268 and 270.
  • Alert conditions which determine under what circumstances an operator is notified of data identified by a trap.
  • a threshold condition set in a software trap is met, depending on the conditions set by the user, either an alert is sent, or a counter is incremented. If the counter is incremented, then the new count is checked against the threshold.
  • the alert action may take several forms.
  • the alert is preferably logged for audit purposes, including the trap condition, the offending monitored resource, the offending values, and a date/time stamp.
  • a local dump of the offending request, method or thread can be produced, as can access to a display.
  • a stack trace and method trace may be provided.
  • One or more individuals may be notified, such as by e-mail or other message such as an SNMP alert. Escalation of the alerts may be included, for example, by sending an e-mail only after the third occurrence of a threshold. Other examples of multiple actions taken on multiple conditions may readily be envisioned.
  • the counter is reset to zero. If a Boolean condition has been specified, the condition is reevaluated each time a boundary is met. If a method has been specified, the condition is reevaluated after the method is detected.
  • a trap/alert log is maintained identifying the entries by date/time stamp, and other information obtained from the alerts. Users may monitor traps while running to view the log and counter. The user may be provided with the capacity to toggle traps between active and inactive status.
  • the program provides the capacity to obtain performance analysis.
  • Information is provided at a relatively high level, and the user has the option of requesting and receiving more detailed information.
  • Information is provided in a format which will be referred to as a report.
  • the user is prompted to select a type of report, as indicated at 305 in Fig. 3, and a high level report, or trend report, is presented to the user, as indicated at 310. From the trend report, the user is provided with the option of selecting a variety of more detailed reports. The user is given the option to obtain successively more detailed reports.
  • the user has the option of comparing performance data in the report against baseline data from a previous time period. Reports include such information as server availability, server resources, business performance, application performance, and database performance from the perspective of the application.
  • API application programmer interface
  • PMI in WebSphere
  • PMI in WebSphere
  • a trend report which is a selected type of report
  • Reports are stored on a server group level. Initially, data is obtained, such as from the API and server and the user's applications. The user may be able to determine the amount of application data to be captured. This amount may be expressed as a percentage of the total request samples that should be stored. The user is prompted to select the application server from which the request samples are taken.
  • the user may be prompted to select the frequency, in terms of time periods, such as minutes, that the user wants the system to take a snapshot of the data.
  • the use of redundant data should be limited.
  • a sampling ratio is defined to determine how much of the data is to be recorded in a performance history database. The user is prompted to set the sampling ratio, thereby limiting the amount of data required for storage in the database.
  • Table 1 shows the metrics, a description of each metric, and the resource from which the data is obtained.
  • Various types of reports may be provided, including a report type showing trends, and a decompose/decomposition report type on a single data point.
  • the user is prompted to provide certain data for the working set, as indicated at 305, and then provides those data, as indicated at 310.
  • These data include the application server or group, the analysis type, the data period, the data interval, the aggregation period, i.e., the way in which the data is grouped, filtering criteria for selecting data points, the type of analysis, such as request, method, SQL, server availability, and application server analysis, and baseline.
  • the user may then select a type of analysis, as indicated at 315.
  • request analysis has been selected, as indicated at 320, users are prompted to select a metric.
  • metrics are throughput, response time, and CPU time, as indicated at 321.
  • a trend analysis is provided, with labels indicating the time interval and application server, as indicated at 322.
  • Users may break down the request trend report by request type or request name, or by server name if the report applies to a server group.
  • the foregoing breakdown may be referred to as a decomposition, as indicated at 323. Users may further break down any one portion of the decomposition. Alternatively, from the trend report, users may obtain details on any one data point. This further breakdown may be referred to as the detail report, as indicated at 324.
  • the detail report may further be broken down into a trace report, indicated at 325, on one record of the detail report.
  • the trace report provides method entry and exit information, as well as selected metrics.
  • the user can drill down to further levels of detail.
  • a method analysis is selected, as at 330, the user is prompted to select a metric, which maybe one of throughput, response time, and CPU time, as indicated at 331.
  • the user is provided the option of limiting the report to such items as a specific request name, request type, or method name.
  • the system of the invention After receiving the selection from the user, the system of the invention generates a report with a trend analysis, as indicated at 332. From the trend report, the user may select a breakdown of the trend analysis by request name or request type.
  • the resulting report will be referred to as a decomposition report for method analysis, as indicated at 333. If applicable, users may decompose a trend analysis report by server, if the report covers a server group. Users may select any portion of the decomposition report for the method analysis for breakdown to detail and view by individual record, or users may select a breakdown of a single data point in the trend report into records.
  • the resulting report is referred to as the detail report, indicated at 334.
  • the user is prompted to select one of the metrics of throughput and response time, as at 341.
  • Users may select a specific request name or request type, method name, table name, or SQL call.
  • the system provides a trend analysis, as at 342.
  • the trend analysis may be broken down by request name, request type, method name, and/or table name to provide a decomposition report, as at 343.
  • the report may include the number of samples as a percentage of total. Users may break down any one portion of the decomposition report to obtain detail by individual records, or break down the trend report by a single data point to obtain individual records.
  • the report with individual records is known as the detail report, as at 344.
  • a trend analysis is provided, as at 351. No metrics are selected.
  • the system may plot the percent up time of the group over a series of time intervals. The user may break down a trend report for a group by application server, as at 352.
  • An application server analysis report may be selected as at 360.
  • the user may be prompted to provide one of the following metrics: pool size, concurrent waiters, average wait time, faults, percentage pool usage, physical connections, JVM free memory, and JVM memory used, as at 361.
  • a trend analysis report is provided, as at 362.
  • Reports may be provided in any suitable manner.
  • Trend reports may be a line graph, with a tablature view of all the data, for each data point.
  • a comparative baseline display may be provided, showing the same data at a selected time past time. For example, baseline data may show the same data for the same time of day on a prior day.
  • decomposition reports a bar or pie graph may be furnished, with a tablature view of all data, per type. The user is preferably able to select a portion of the decomposition report to drill down to a detail report. Baseline data may be provided in the detail report for comparison.
  • Software Consistency Check
  • the program of the invention obtains runtime environment data as to how a system is set up and installed.
  • These environments may be system, Java, and application server.
  • the environment information may include CPU speed, number of CPUs online, number of CPUs offline, memory, operating system version, and physical disk space. Other information may be included.
  • the information may include JDK version, installation directory, Java policy, operating system information, class path, and library path.
  • the information may include the application server, startup directory, listening ports, SSL listening ports, number of registered servlets, number of registered EJBs, number of JDBC connection pools, and number of EARs.
  • the program can prompt a user to select a server as an authoritative server, as indicated in Fig. 4 at 405, receive a selection, as indicated at 410, and then prompt the user to select a server for comparison, as indicated at 415.
  • the system obtains and displays the comparison results, as indicated at 425.
  • the comparison results may include the runtime environment information noted above.
  • the comparison results may contain only the differing data, and may be graphically represented.
  • the system preferably permits a user to drill down from the displayed results to a detail screen displaying all of the relevant information for each application server, as indicated at 430, 435.
  • comparison of binary files with matching file names can be performed.
  • a user is prompted to select one server from a group as an authoritative server, as indicated at 505 in Fig. 5.
  • the user provides a selection, as indicated at 510, and is then prompted to select one or more servers as comparison servers, as indicated at 515.
  • the comparison server(s) selection at 520, the user is prompted to select the source of files, as at 525.
  • the user may select from a list of EAR folders, or the CLASSPATH that is deemed to form the master file list of the authoritative server.
  • the user provides the selection, as at 530.
  • the user is also prompted, as at 535, to select one of the file types for the composition of the master file list.
  • the file type is received, at 540.
  • the system starts preparing the master file list from the selected source and file types from the authoritative servers.
  • the system searches for files listed in the master file list in the comparison servers, as indicated at 545. For each comparison, the results are displayed, at 550.
  • the results may be divided into found files and files not found.
  • the list includes matched files, i.e., all files with matched file name, size, and files system timestamp; like folders, i.e., files with matched file name and size, but not timestamp, and unlike folders, i.e., files.with matched file name only.
  • the files are divided into files in the authoritative server but not the comparison server, and all the files in the comparison server but not the authoritative server.
  • These lists of files are displayed. This display permits the user to readily compare the files in the authoritative and comparison servers. [0070] From this display, the system permits the user to drill down to obtain additional information about the files. The user may select one comparison server, and select one file from the authoritative file, for detailed comparison, as indicated at 555.
  • the system will perform a comparison on the files, with the result being either "same” or "different.”
  • the comparison may use a checksum calculation, such as the MD5 algorithm. It should be noted that, in one embodiment, a further level is required for JAR files before the comparison can be run. First, archive files are extracted, and then name matching is performed. Then the comparison may be run. As a result of these comparisons, both the names of the files and the contents of the files are compared between servers, as indicated at 560. Such problems as variant versions and corrupted code can readily be identified. Request Rewrite.
  • a method, system and program may be provided for rewriting or mapping certain requests.
  • three different types of requests are received in a system of the invention. These are JSPs, servlets, and remote Enterprise Java Bean calls. These requests are typically in the form of strings, and are received from another application, such as a web server or another application server. Such requests are employed in the system of the invention for two different purposes. The requests may be used for identification purposes. The requests may also be used to represent a business request or an application. In general, the implicit dual meanings of a request string are not problematic. However, there are situations in which these dual meanings can create conflicts.
  • request strings in the form of an URL normally look exactly the same, and therefore convenient for the end users to memorize; however, they are deemed to be different types of request by the portal engine using the underlying data object, such as a request or a session object.
  • the underlying data object such as a request or a session object.
  • an operator or administrator will be confused as he will see requests for different functions represented by the same string, with no resolution between the strings.
  • a single application may involve multiple and different request strings and after their successful executions, the resulting performance data is to be analyzed against one application name or label.
  • the problem here again is that there is a lack of a group mechanism for the system to recognize that a group of request strings are related to each other.
  • a module which may be in the form of Java based logic, may be provided to map requests. As indicated in Fig. 6, each request, such as request 600, is mapped to two separate strings: a distinguishable request string 605, and a collapsible request string 610. These separate strings are used for distinct purposes. These strings may be a distinct URL, or a label string.
  • the mapping or rewriting operation preferably takes place at a point when both problem determination and performance management functions may take advantage of the operation. For example, performance management functions would perform decomposition by request on the collapsible request string.
  • An active request search used in problem determination, is conducted on distinguishable request strings.
  • Security is preferably maintained by providing that each user is assigned to a user role. Each user role is mapped to particular functions of the software of the invention. An access control list may be provided with the mapping between the product functions and the user roles associated with them. An administrator may add user roles and map those roles to functions. Referring to the schematic illustration in Fig. 7, and administrator 700 has read and write access to all functions and configurations, and access to log files. For example, creation, modification, activation, deactivation, and deletion of software traps, and changing of monitoring levels, may be for the administrator only. An operator 705 has display access to most functions, and access to certain function configuration. A user 710 has display access to functions and reports, but not to any function configuration.
  • the system of the invention may have the architecture described below.
  • the architecture may be in the nature of an agent operating on each application server, and the remaining components on a dedicated server, including a kernel providing central control, a publish server for receiving data from the probe engine, an archive agent for moving data from the cache to a database, a database, a visualization engine for providing all end user applications, and an application server agent for collecting certain application server specific data from an application server (such as Websphere).
  • An exemplary architecture is illustrated at Fig. 8.
  • Application server agents such as one shown at 2510, are installed on application servers.
  • Probe and publish engine 2511 is the principal component of application server agent 2510.
  • the remaining components may be installed on dedicated server 2520.
  • Kernel 2530 provides central control.
  • Publish server 2540 receives data from application server agent 2510 and moves data to archive agent 2550.
  • Archive agent 2550 moves data to database 2560.
  • Visualization engine 2570 proves all end user applications, and communicates with the database for historical information, and directly with the application server agents 2510 to request and receive snapshot information.
  • the source of the data provided to the user in the method described above may be a probe and publish engine.
  • the probe and publish engine obtains all information pertaining to specific threads.
  • the standard Java profiling interface (JVMPI) may be employed for probe agents.
  • JVMPI Java profiling interface
  • probe and publish engine 2511 is shown in relation to the Java virtual machine 2610 with which it communicates, as well as the application server 2615.
  • Probe and publish engine 2511 preferably has five components: the probe controller 2512, command agent 2513, event agent 2514, event handlers 2515, and the publish engine 2516.
  • Probe controller 2512 is a controller thread that controls the life cycle of the other components.
  • Event agent 2514 registers the event handlers for JVMPI events of interest. When such events occur, the handlers are then invoked. The handlers collect the relevant information and add it to an event queue.
  • Publish engine 2516 then obtains the data from the event queue and sends it to the publish server 2540.
  • the agents may be constructed using the standard Java profiling interface provided with Java Development Kit 1.2.2 or above.
  • a JVMPI library is loaded with the JVM, and communicates with the JVM, the probe controller, the event agent, and the command agent.
  • JNI functions may be used to capture all event-based data, and date/time stamp, wall clock and CPU clock. Events that are registered by the JVMPI library, event agent, command agent, publish engine, and probe controller, are shown at Table 2:
  • Event queue Information obtained from the JVMPI library is stored in an queue, called the event queue, and the event agent retrieves records from the queue, packs them in a packet, and sends them to the publish server via the publish engine.
  • the data collected from the queue by the Event Engine are shown at Table 3:
  • the Command Agent is an RMI service registered with the kernel.
  • the Command Agent receives commands from the visualization engine and other external components and satisfies them using JVMPI or JNI calls.
  • JVMPI Joint Photographic Experts Group
  • JNI JVMPI
  • An exemplary list of commands, and whether the commands are provided to the JVMPI or the JNI is shown at Table 4.
  • the probe controller is also preferably an RMI service registered to kernel 2530, and starts and stops other probe components gets the probe's configuration. New configurations of probes are sent from kernel 2530 to the probe controller. The probe controller will determine if a probe should be started or stopped or a filter changed upon receiving a new configuration.
  • a logic diagram for the Probe/Publish Engine is provided as Fig. 10. In accordance with this logic diagram, when the JVM is loaded, at shown at 2702, events identifying thread starts, thread end and completion of initialization of the JVM are registered through JVMPI to the kernel, as shown at 2704. When initialization of the JVM is completed, as indicated at 2706, then the system properties are set and a thread for initiating probes is created, as indicated at 2708.
  • the thread then enables the method entry and class load events, as indicated at 2710, and waits until the application server has started, as shown at 2712.
  • a method entry starts a process flow in the JVM, at 2714, which checks to see if the application server is started, at 2716. If it is started, the process flow is passed to the InitProbe Thread, which disables method entry and class load events, at 2718, and creates a probe controller thread, at 2720.
  • the probe controller thread seeks a probe configuration from the kernel, at 2722. If the probe configuration is not found, then the flow ends, as indicated at 2724 and 2726. If the configuration is found, the process flow proceeds to determination if the probe is enabled in the configuration, at 2728. If not, then the process flow ends.
  • a process flow may also commence with a new configuration in the form of an RMI call from the kernel, as indicated at 2730. If the probe is enabled, then the process flow proceeds to start the event agent and command agent, enable a class load events and a method entry events, as shown at 2732.
  • the command agent awaits a command from the visualization engine, as indicated at 2734 and 2736.
  • the enabling of the method entry event starts a process flow in the JVM, as indicated at 2750.
  • Data such as CPU clock, wall clock, method identification, thread identification, and/or URL and SQL are obtained, as indicated at 2750, and passed to event queue 2760.
  • the class load event initiates a process flow in the JVM, as shown at 2754.
  • a function of get class name, method name and signature is initiated, as shown at 2756, and this information is passed to class hash table 2762.
  • the event agent retrieves records from the event queue 2760, as indicated at 2780. The event agent will wait depending on the publishing frequency, as indicated at 2782.
  • Visualization engine 2750 provides the front end user interface component used in the method and system of the invention. Standard J2EE technologies may be used for implementation of visualization engine 2750.
  • the front-end framework of visualization engine 2750 handles housekeeping such as session management and security.
  • the visualization engine 2750 preferably handles as many common tasks as possible in order to provide an environment conducive to the development of front- end application and business logic components.
  • the visualization engine 2750 sits on top of a database, which it accesses in response to user requests.
  • the architecture is illustrated at Fig. 28, and is shown to be browser-based, using a browser 2810, communicating with a web server 2815, which may be an Apache web server, and an application server 2820, such as IBM's Websphere, interfacing between the database and the web server.
  • Servlets may be used to handle requests and manage application flow. Servlets may also be employed to control front-end behavior by performing form data-entry validation and sending java bean objects containing data to JSP pages. JSP pages may handle most of the front-end presentation logic. Business logic may be implemented using enterprise java beans Generally, stateless session beans are used.
  • Servlets may be used for form-entry data validation, as noted above, and for application logic flow.
  • a base servlet may be provided that all servlet applications must extend.
  • the base servlet sets up global variables, handles authentication and authorization, and performs redirects to login and access-denied pages as necessary.
  • Resource bundle, log message and audit trail message files are provided.
  • the JSP's generate HTML code to render the web page to be displayed in the browser.
  • Servlets pass the desired data to the JSP's using java bean objects.
  • the top layer of the stateless session beans makes up the API. There may be a layer of enterprise java beans or java classes below the top layer that deals with access to data from the database. Data from the database may be obtained through a database access layer that is part of the DB Access data access framework.
  • the application activity display function provides real-time access to data, as noted above, and involves direct communication between the visualization engine and the corresponding publish server and probes. A publish server interface and command agent interface are provided for this direct communication. The stubs to these interfaces are maintained by the kernel, and are retrieved by the visualization engine by performing a lookup from the kernel using a lookup agent helper client. Each server in which probes are running has a unique identification for the probe.
  • the interface stub of the command agent is obtained from the kernel.
  • the identification of the publish server used by the probe is then obtained from the probe.
  • the corresponding interface stub of the publish server is obtained from the kernel.
  • the visualization engine includes the security functions discussed above.
  • a proprietary API was developed because the J2EE specification security features are not sufficient to provide the security features described above.
  • Security features consist of authentication and authorization functions. Authentication is performed via a proprietary Java API that wraps a third party authentication system. Authorization is performed by maintaining access control lists by users or groups. A user is associated with specific groups and can only access data for servers in those groups. Servers are each associated with one or more groups.
  • the kernel enables various services to discover each other on a network and provides a way for services to interact in a dynamic, robust way. No user intervention is required when services are brought on or offline. Services that join the kernel can adapt dynamically when any of the other services go on or offline. Consumers of the services do not need prior knowledge of the service's implementation.
  • Fig. two instances of the kernel, 2530 and 2530', are shown.
  • the architecture of the kernel features a core 2531, a lease administrator 2532, an RFS server 2533, a codebase server 2534, a registration database 2535, an availability server 2536, and a configuration server 2537. Two instances of the kernel are preferably running on separate servers for enhanced availability.
  • the kernel core 2531 handles all join, renew, leave and lookup requests from a service.
  • the services are probe agents, the availability server 2536, and the configuration server 2537.
  • the service passes a proxy object and its associated service attributes to the kernel.
  • the kernel fulfills the request by storing the proxy object and service attributes in the registration database.
  • a client needs a certain type of service to accomplish a task, it looks for the service by passing a search template and issuing a lookup request to the kernel. Based on the search template, the kernel will return the corresponding proxy object to the client.
  • Each service is required to renew its lease by issuing a renew request to the kernel periodically.
  • the kernel If the kernel does not receive a renew request when required, the kernel removes the service's proxy object and service attributes from the registration database. This renewal requirement avoids requests being sent to services that are unavailable.
  • the probe and publish server preferably bundles the application and system information, such as the volume of completed requests and CPU utilization, when the lease is renewed. The lease concept thus serves to report the availability of the server and high-level statistical information. A service may also issue a leave request to the kernel.
  • the lease administrator component 2532 keeps track of the records in the registration database. If any registration is expired, or a leave request is received, the lease administrator 2532 causes the corresponding record to be removed so that the kernel will not pass the corresponding proxy object to any clients.
  • the RFS (request for stub) server 2533 listens on a port for connections. When a connection is identified, a serialized stub object of the kernel is sent out to the service or client to use in interfacing with the kernel.
  • the codebase server 2534 is similar to an HTTP server, but provides a facility to allow clients of a service to download the class definitions of the proxy object it obtains from the kernel.
  • the registration database 2535 provides in-memory storage for proxy objects and associated service attributes. Server availability and statistical information resides in the registration database 2535. [0087]
  • the availability server 2536 takes snapshots and stores the history of the registration database 2535 in order to facilitate providing availability of servers and statistical data to the visualization engine 2570.
  • the configuration server 2537 is a centralized place to store configuration data for all components. Configuration data is in XML form and is kept in the database. Users may change configuration through the visualization engine. When this is accomplished, the configuration server 2537 retrieves from the kernel a list of proxy objects that are adapting to the old configuration. The configuration server 2537 makes use of the proxy objects to broadcast the new configuration. This serves to update the configuration of probes in response to user commands at the visualization engine.
  • a helper utility called JoinManager, requests the stub object of the kernel, and joins the kernel with the proxy object as well as its service attributes. If the stub object is not available, the utility will continue to retry until it succeeds. This utility also maintains and renews the lease.
  • a lookup manager utility may be used by a client to look up a specific service.
  • the publish server 2540 manages data received from the various publish engines. Multiple publish servers may be provided in a single installation. The publish server provides query capabilities for the visualization engines. The publish server also manages the incremental retrievals of performance management related data and system resources related data.
  • the publish server architecture is shown at Fig. 13.
  • Publish server 2540 may be implemented as a multithreaded process. Each thread connects to a specific publish engine and receive data from it. It may also contain additional threads to deal with startup, shutdown and communications to the kernel.
  • publish server 2540 spawns a thread to join the kernel, and regularly renews its contract, as shown at 3002.
  • Publish server 2540 also spawns a thread to accept socket connections, as indicated at 3004.
  • decision block 3006 the next step depends on whether a query is received from the corresponding publish engine. If, rather than a query, data is received, a persistent socket connection is established, as indicated at 3008. The data is also associated with a request. Data is then obtained from the probe via the publish engine, as indicated at 3010. If a server restart signal is received, as indicated at 3012 and 3014, then the publish server resets the accumulated data for the restarted server before proceeding.
  • the server is registered so that the server's performance management related data and system resources related data will be retrieved periodically, such as every 5 minutes.
  • the process flow then proceeds to processing the records, such as method level records, class load records, and GC records, received from the probe, as indicated at 3020. If a request is completed or there is no activity on the request for a certain amount of time, as indicated at 3022, then the request is removed from the active request list, as indicated at 3024. The process flow then returns to accept more data from the probe, as indicated by labeling leading from 3026. [0093] If the data is determined to be a query, then a property may be used to determine the appropriate type of information.
  • Queries may ask for various information, as illustrated at 3030, 3032 and 3034.
  • the result is then serialized and sent back to the publish engine.
  • the publish server also receives certain administration requests made by its clients, such as for status, as indicated at 3036, and stop the service, as indicated at 3038. These tasks can be invoked by administrators.
  • the connection is closed when the information in response to the query has been provided, as indicated at 3040, and the publish server becomes available to accept socket connections again.
  • the visualization engine comprises means for presenting information to a user, means for prompting a user, and means for receiving requests from a user.
  • the probe engine comprises means for obtaining information regarding distributed applications, and for carrying out filtered monitoring of the distributed applications. It will be understood that the functions of the publish engine, archive, database and kernel cooperate with the visualization engine and the probe engine to provide one means for carrying out the steps of the method.
  • a method and system may be provided for conducting analysis of internal components of the architecture, and for reporting the results of the analysis to an operator.
  • the kernel view indicates all running instances of the kernel component of a software system of the invention. For each instance, there is provided a kernel runtime environment detail and a component overview for each. Exemplary values in a kernel runtime environment detail include the platform, the D? address, various port numbers, a codebase library path, contract renewal interval, the start time, the file where the security policy is resident, driver names, and the URL of its corresponding database.
  • the component overview may include the service name, the component identification, platform, D? address, the listen port number, the first join time, and the last contract renewal time.
  • Each component identification in the component overview section may be a link to provide a corresponding view.
  • a data collector component view displays data pertaining to all up and running data collector controllers.
  • the first two sections provide configurations and environment in which the data collector controllers are running.
  • the publish server relationship section displays the identity of the publish server to which the data collector is connecting.
  • the identities include component LD, the identity of the admin server, the identity of the application server, the identity of the platform, the D?
  • a publish server view provides information as to all up and running instances of the publish server component. For each instance, there may be four sections: publish server runtime environment detail, the data collector relationship, the PMI agent relationship, and the archive agent relationship.
  • An archive agent view shows all up and running instances of archive agent and for each instance of archive agent, there are two sections of information: the archive agent runtime environment detail, and the publish server relationship.
  • the archive agent runtime environment detail lists the configuration and the environment of the archive agent.
  • the publish server relationship information identifies the publish server that the archive agent is serving.
  • the system of the invention may be installed through installation of certain probe software on a server to be monitored, and a separate server for the remaining software of the invention. This configuration provides for relatively straightforward installation of the system of the invention.
  • the present invention can be embodied in the form of methods and apparatus for practicing those methods.
  • the present invention can also be embodied in the form of program code embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.
  • the present invention can also be embodied in the form of program code, for example, whether stored in a storage medium, loaded into and/or executed by a machine, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention.
  • program code When implemented on a general-purpose processor, the program code segments combine with the processor to provide a unique device that operates analogously to specific logic circuits.

Abstract

A method for management of performance of computer systems and applications includes prompting the user to select information for monitoring, monitoring the performance of applications running on servers, displaying data, and prompting users to input performance adjustments. A user is prompted to select a server or server group, a resource, and a threshold or condition for notification, and in response a system compares the value or quality of the parameter to the threshold or condition, and provides a notification to the user in the event that the parameter reaches the threshold or condition. A method includes the steps of providing the user with performance information, receiving from the user a request for more specific performance information, and providing more detailed performance information. A method according to the invention includes the steps of receiving from the user an identification of a server as an authoritative server, another server as a comparison server, comparing runtime environment data in the form of one or more of CPU data, server data and Java data between the selected servers, and displaying differences to a user. A method of the invention includes the steps of receiving from the user an identification of a server as an authoritative server, and another server as a comparison server, and providing a list of matching and differing file names. The method may further include the step of receiving from the user a selection of a file, conducting a comparison of the files, and providing a result to the user. A method of the invention includes the steps of assigning a role to each user, and mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user.

Description

METHOD AND SYSTEM FOR MONITORING PERFORMANCE OF APPLICATIONS IN A DISTRIBUTED ENVIRONMENT
FIELD OF THE INVENTION [0001] This invention relates to computer software, and in particular to distributed computing.
BACKGROUND OF THE INVENTION [0002] Business-critical applications are currently hosted on distributed servers using Sun Microsystems Java 2 Enterprise Edition (J2EE) technologies. Such applications include servers providing key business operations directly to customers running browser clients. A variety of tools and techniques are available to monitor the performance of various components of such systems, including databases, platforms, and hardware. However, the performance experienced by the customer is not the performance of such underlying components, but the performance of the application. The inventors have identified a key failure in the prior art to provide information on the performance of the application.
[0003] As a result of the inability of prior art products to measure performance of the application, decisions about selections of hardware and software maybe ill-informed. For example, if an application is responding slowly, one option available to managers is to purchase or lease additional servers on which the application runs. Such purchases are expensive, and the installation of new hardware employs information technology personnel who are necessarily diverted from other tasks. Other responses to an application responding slowly include changing of configurations of various hardware. However, numerous different combinations of various hardware and software configurations may need to be tried in order to improve application performance.
SUMMARY OF THE INVENTION [0004] A method in accordance with the invention for monitoring the performance of applications running on a server in a distributed computing environment comprises the step of prompting the user to select information for monitoring, monitoring application performance in accordance with the selected information, and making the monitored performance information available to the user.
[0005] A method in accordance with the invention includes the steps of prompting a user to select a server or server group, a resource, and a threshold or condition for notification, comparing the value or quality of the parameter to the threshold or condition, and providing a notification to the user in the event that the parameter reaches the threshold or condition.
[0006] A method according to the invention comprises the steps of providing the user with performance information relating to applications running on a server in a distributed computing environment, receiving from the user a request for more specific performance information, and providing more detailed performance information in response to the request.
[0007] A method according to the invention includes the steps of receiving from the user an identification of a server as an authoritative server, another server as a comparison server, comparing runtime environment data in the form of one or more of CPU data, server data and Java data between the selected servers, and displaying differences to a user.
[0008] A method of the invention includes the steps of receiving from the user an identification of a server as an authoritative server, and another server as a comparison server, and providing a list of matching and differing file names. The method may further include the step of receiving from the user a selection of a file, conducting a comparison of the files, and providing a result to the user.
[0009] A method of the invention includes the steps of receiving a request string, and mapping the received request string to a distinguishable request string and a collapsible request string. The received request string may be in the form of a JSP, a servlet, and remote Enterprise Java Bean calls. A method of the invention may prompt a user to create rules for mapping of a received request string to a distinguishable request string and a collapsible request string.
[0010] A method of the invention includes the steps of providing, in a system running at least one application, a management application having various components for monitoring and management, and monitoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components.
[0011] A method of the invention includes the steps of assigning a role to each user, and mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user.
[0012] A system in accordance with the invention for monitoring the performance of applications running on a server in a distributed computing environment includes computer hardware and software for prompting the user to select information for monitoring, computer hardware and software for monitoring application performance in accordance with the selected information received from the user, and computer hardware and software for making the monitored performance information available to the user.
[0013] A system in accordance with the invention includes computer hardware and software for prompting a user to select a server or server group, a resource, and a threshold or condition for notification, computer software and hardware for comparing a value or quality of a monitored parameter of the resource on the server or server group to the threshold or condition, and computer software and hardware for providing a notification to the user in the event that the parameter reaches the threshold or condition.
[0014] A system according to the invention includes computer hardware and software for providing the user with performance information relating to one or more applications running on a server in a distributed computing environment, computer hardware and software for receiving from the user a request for more specific performance information, and computer hardware and software for providing more detailed performance information in response to the request.
[0015] A system according to the invention includes computer hardware and software for receiving from a user an identification of a first server as an authoritative server and a second server as a comparison server, computer hardware and software for comparing runtime environment data from the authoritative server and the comparison server in the form of one or more of CPU data, server data and Java data between the selected servers, and computer hardware and software for displaying differences in such data between the selected servers to a user.
[0016] A system according to the invention includes computer hardware and software for receiving from the user an identification of a first server as an authoritative server and a second server as a comparison server, and computer hardware and software for providing a list of matching and differing file names. The system may further include computer hardware for receiving from the user a selection of a file on both the authoritative server and the comparison server, computer hardware and software for conducting a comparison of the files, and for providing a result to the user. [0017] A system of the invention includes computer hardware and software for receiving a request string, and computer hardware and software for mapping the received request string to a distinguishable request string and a collapsible request string. The received request string may be in the form of a JSP, a servlet, and remote Enterprise Java Bean calls. A system of the invention may include computer hardware and software for prompting a user to create rules for mapping of a received request string to a distinguishable request string and a collapsible request string. [0018] A system of the invention includes computer hardware and software for providing, in a system running at least one application, a management application having various components for monitoring and management, and for monitoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components. [0019] A system of the invention includes computer hardware and software for assigning a role to each user, and computer hardware and software for mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user. [0020] A computer program in accordance with the invention for monitoring the performance of applications running on a server in a distributed computing environment, consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of prompting the user to select information for monitoring, monitoring application performance in accordance with the selected information, and making the monitored performance information available to the user.
[0021] A computer program in accordance with the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of prompting a user to select a server or server group, a resource, and a threshold or condition for notification, comparing a detected value or quality of a parameter of the resource on the server or server group to the threshold or condition, and providing a notification to the user in the event that the parameter reaches the threshold or condition.
[0022] A computer program according to the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of providing the user with performance information relating to applications running on a server in a distributed computing environment, receiving from the user a request for more specific performance information, and providing more detailed performance information in response to the request. [0023] A computer program according to the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of receiving from the user an identification of a first server as an authoritative server, a second server as a comparison server, comparing runtime environment data in the form of one or more of CPU data, server data and Java data between the selected servers, and displaying differences to a user. [0024] A computer program according to the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of receiving from a user an identification of a first server as an authoritative server, and a second server as a comparison server, and providing a list of matching and differing file names between the first and second servers. The program may further include instructions which, when executed on a processor, cause the processor to execute the steps of receiving from the user a selection of a file found on both the first and second servers, conducting a comparison of the files, and providing a result to the user.
[0025] A computer program of the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of receiving a request string, and mapping the received request string to a distinguishable request string and a collapsible request string. The received request string may be in the form of a JSP, a servlet, and remote Enterprise Java Bean calls.
[0026] A computer program of the invention consists of instructions stored on a medium, which instructions, when executed on a processor, causing the processor to execute the steps of providing, in a system running at least one application, a management application having various components for monitoring and management, and monitoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components. [0027] A computer program of the invention consists of instructions stored on a medium, which instructions, when executed on a processor, cause the processor to execute the steps of assigning a role to each user, and mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user. BRIEF DESCRIPTION OF THE FIGURES [0028] Fig. 1 is a flow diagram illustrating a method in accordance with the invention.
[0029] Fig. 2A and 2B is a flow diagram illustrating a method in accordance with the invention.
[0030] Fig. 3 is a schematic illustration of a method in accordance with the invention. [0031] Fig. 4 is a flow diagram illustrating a method in accordance with the invention.
[0032] Fig. 5 is a flow diagram illustrating a method in accordance with the invention.
[0033] Fig. 6 is a schematic diagram illustrating a feature of the invention. [0034] Fig. 7 is a schematic diagram illustrating a feature of the invention. [0035] Fig. 8 is a schematic diagram illustrating an exemplary architecture. [0036] Fig. 9 is a schematic diagram illustrating features of an exemplary architecture.
[0037] Fig. 10 is a diagram illustrating features of an exemplary architecture. [0038] Fig. 11 is a schematic diagram illustrating features of an exemplary architecture.
[0039] Fig. 12 is a schematic diagram illustrating features of an exemplary architecture. [0040] Fig. 13 is flow diagram illustrating an exemplary architecture.
DETAILED DESCRIPTION [0041] The invention includes a process for monitoring and providing information about the performance of certain aspects of computer systems, and computer programs and systems for accomplishing these purposes. The method and system will be described with reference to a computer program for accomplishing these purposes and for use in a system of the invention. The computer program of the invention is particularly useful for applications running on application servers. The computer program of the invention includes a user interface providing a variety of information and options to the user. Probes installed on application servers obtain information related to the operation of the applications and servers and furnish that information to other program elements for analysis and reporting to the user. Monitoring Levels and Schedule
[0042] In a method, system and computer program in accordance with the invention, there is provided a capability for providing selected levels of detail about the operation of applications running on a server. A user is prompted to identify information for monitoring, as indicated in Fig. 1 at 105. A user is preferably provided with at least two choices as to the level of detail of monitoring. The term level of detail of monitoring refers to the amount and nature of information that is obtained about the running of the applications. The level of detail of monitoring may refer to the amount of data or information that is being obtained. The level of detail may also refer to the nature of the information that is being obtained. For example, some types of information, such as server availability information, are at a relatively high level of detail. Other types of information, such as method trace information, are at a relatively low level of detail.
[0043] The user may be prompted to select a level of monitoring. The user may select particular features to monitor. Alternatively, preselected monitoring levels may be provided. Each preselected monitoring level has associated therewith particular information that is monitored and reported. Upon receiving from a user a selection of a monitoring level or particular features, as indicated at block 110 of Fig. 1, the program of the invention monitors application performance, as indicated, and makes the monitored performance information available to the user. In one example, illustrated in Fig. 1, three levels of monitoring may be provided. Upon receipt of the request from the user, the system determines the monitoring level, as indicated by decision block 115. At Level 1, the highest level, and therefore the level providing the least information, the information may be in the nature of request level data and server level data. For example, the associated information may be availability management, system resources and distributed platforms, and basic request data, as indicated at block 120. Availability management includes information as to whether a particular application is running on a particular server. System resources indicates such information as the amount of available memory and number of available connections. Basic request data indicates the number of requests being made, the number of requests being completed, and the like.
[0044] In the same example, the user may be provided with a selection of Level 2 monitoring. A Level 2 monitoring selection ordinarily include all of the information provided by Level 1 monitoring, with additional information, as indicated at block 125. The additional information may be API level data, such as SQL data, JMS data and EJB call data. Such data may include data regarding the throughput of a particular CPU. The functionality to permit the user to provide a soft cancel of a request may be provided. No method data or SQL level data is provided. In order to provide the additional data, the JVMPI is enabled on the corresponding JVMs. This level is directed at problem determination, and may be used for servers with a high volume of transactions, with occasional instability. The complexity of the transactions may vary. Because the JVMPI is enabled on the corresponding JVM, the user may be provided with the option of changing dynamically to a more detailed level of monitoring, such as Level 3 described below.
[0045] In the same example, the user may be provided with a selection of Level 3 monitoring. Level 3 monitoring provides the information furnished in connection with Level 2 monitoring, plus method level data. Level 3 may include advanced problem determination and reporting, including, for example, method and SQL level data, as indicated by block 130. The JVMPI is enabled on the corresponding JVMs. JVMPI function calls are possible, and method entry and exit events are selected. This level is typically used for servers which have been selected for diagnostics, detailed workload characterization and profiling. Since this level requires enabling of the JVMPI, as noted above, it is possible to dynamically change between this level and other levels in which the JVMPI has been enabled, such as the exemplary Level 2 described above. In all cases, as noted above, and as indicated by block 135, monitored information is presented to the user.
[0046] In a preferred embodiment, the user is prompted to define a schedule for monitoring, as indicated by block 140. The schedule is received from the user, as indicated by block 145, and monitoring proceeds in accordance with the schedule as indicated by block 150. A schedule defines at least a start time, preferably defined by calendar date and time, a monitoring level, and a server or group of servers. Rather than a monitoring level, the program of the invention could permit the user to select individual data items for monitoring. The schedule may define times for the monitoring level to change, which may also be in terms of a calendar date and time. The schedule may be selected to cycle on an appropriate basis, such as each month, each week, or each day. In a preferred embodiment, a schedule consists of a group of schedule records, each of which is a combination of a start date and time and a monitoring level. The program of the invention causes monitoring to commence with the first schedule record, and monitoring to change when the current time is the start time and date of another schedule record. This process continues through successive schedule records. A default monitoring level may be provided for use at a time when no monitoring is specified in the schedule. The program may be furnished with a default, which may be changed by the user. The user is prompted to apply a completed schedule to one or more servers or server groups. The user may be provided the option to duplicate an existing schedule, and then be prompted for servers and server groups to which to apply the schedule. The user may be provided the option of modifying the fields of a schedule. Preferably, if a schedule is modified by removal of a server or server group, the user will be prompted to apply another schedule to that server or server group. The program may be configured to prevent the user from removing all schedules from a given server. Alternatively, upon removal of all schedules from a given server or group, monitoring of the affected server or server groups may return to a default monitoring level. The user may be provided the option of deleting a schedule, and monitoring may take place at a default level for the time and server or server groups corresponding to the deleted schedule. [0047] While a programmed monitoring level, with the items to be monitored preselected, may be used, a system of the invention may permit a user with proper authorization to manually change the items to be monitored. Such a manual change would preferably only be available on a temporary basis, and may be limited to a particular server or server group.
[0048] If a server is restarted, the system follows a hierarchical search path to determine the proper level of monitoring. If it is possible to contact the scheduler, ask for a temporary override, and then a scheduled monitoring level, then the system- wide monitoring level is used. When the scheduler cannot be contacted, then the default monitoring level is used. Monitoring Traps and Alerts
[0049] In a method, system and computer program according to the invention, while monitoring of a server is taking place, alerts are provided to the user. Alerts are provided as a result of a parameter of a monitored resource on a selected server or server group reaching a selected matching condition or threshold value for that condition. The software that is capable of providing a notification or alert to the user is referred to here as a software trap. The user may select the option of creating or modifying a software trap from a menu in a program according to the invention. There are a number of selections which a user is prompted to make in order to create a new software trap. These selections include the servers or server groups on which the trap will be applied, the resource to be measured, and the condition. As indicated in the example of Fig. 2, the first step may be to prompt the user to select a server or server group, as indicated at block 205. The selection is received, as indicated by block 210.
[0050] The information required varies with the type of trap, and the user is prompted for the type of trap, as indicated at block 215.
[0051] For a first type of trap, as indicated in decision block 220 and block 225, a resource and a condition in the form of a threshold value must be selected. Resources may include occurrence, CPU time, resident time, wait time, and SQL resident time. Threshold values would depend on the particular type of resource. Upon selection of the resource, as at 230, the system may provide the units to the user for selection of the threshold value. The trap can be applied to any request, to a specific request name, or to a specific method name. The trap then proceeds to monitor the selected resource, as indicated by block 235. If a threshold is met, then the system evaluates whether an alert condition has been triggered, as indicated at blocks 236 and 237. If not, then the event may be logged, as indicated at block 238. If an alert condition is met, then an alert is communicated to a user and recorded, as at 239. [0052] For a second type of software trap, as indicated in blocks 240 and 242, a resource and condition with a number of hits must be selected. To set this type of software trap, the user is prompted to specify a resource and a condition, as at 242. The resource may be, for example, an HTTP request parameter, or an SQL statements. For an HTTP or SQL request, a condition is a specified string contained in the HTTP/SPL request. The condition may also be in the form of a Boolean expression applied to strings. When the user provides the requested resource and condition, at 244, the software trap performs monitoring, as at 246 of Fig. 2B. Whenever a request or statement is identified meeting the condition, a hit counter is incremented, as indicated by blocks 248, 250 and 252 in Fig. 2B. If sufficient hits are counted, then an alert condition is reached, and an alert is communicated and recorded, as at 254.
[0053] A third type of trap applies to the condition of the resource consumption of the application server. The user is required to select an application server or group. The user is prompted to specify, for resource and threshold values, a resource, and a threshold, as indicated by blocks 260, 262 and 264 in Fig. 2B. The resources may include information relating to application server availability, database connection pools, and JVM runtime memory. Server availability is measured as a simple positive or negative. As to database connection pools, a number of different thresholds may be set, including: number of connections allocated to number of connections; average number of threads waiting for a connection; average time that a client waits to be granted a connection; number of connection pool timeouts; and average percent of the pool in use. For JVM runtime memory, resources may be the amount of free memory in the JVM runtime and the amount of memory used in the JVM runtime. The user is prompted to provide a number and to indicate whether that number is a maximum or minimum. Suitable units may be provided to the user, e.g., Mbytes for free memory and memory used. The user is also prompted to select the number of times that a condition is met before an alert message is created. The resource is momtored, as indicated at 266, and if an alert condition is met, an alert is communicated and recorded, as shown at 268 and 270.
[0054] Alert conditions, which determine under what circumstances an operator is notified of data identified by a trap, will now be described. In operation, when a threshold condition set in a software trap is met, depending on the conditions set by the user, either an alert is sent, or a counter is incremented. If the counter is incremented, then the new count is checked against the threshold. The alert action may take several forms. The alert is preferably logged for audit purposes, including the trap condition, the offending monitored resource, the offending values, and a date/time stamp. A local dump of the offending request, method or thread can be produced, as can access to a display. A stack trace and method trace may be provided. One or more individuals may be notified, such as by e-mail or other message such as an SNMP alert. Escalation of the alerts may be included, for example, by sending an e-mail only after the third occurrence of a threshold. Other examples of multiple actions taken on multiple conditions may readily be envisioned. When a threshold number of hits is detected, the counter is reset to zero. If a Boolean condition has been specified, the condition is reevaluated each time a boundary is met. If a method has been specified, the condition is reevaluated after the method is detected.
[0055] A trap/alert log is maintained identifying the entries by date/time stamp, and other information obtained from the alerts. Users may monitor traps while running to view the log and counter. The user may be provided with the capacity to toggle traps between active and inactive status. Application Performance Analysis
[0056] In a method, system and computer program of the invention, the program provides the capacity to obtain performance analysis. Information is provided at a relatively high level, and the user has the option of requesting and receiving more detailed information. Information is provided in a format which will be referred to as a report. In general, the user is prompted to select a type of report, as indicated at 305 in Fig. 3, and a high level report, or trend report, is presented to the user, as indicated at 310. From the trend report, the user is provided with the option of selecting a variety of more detailed reports. The user is given the option to obtain successively more detailed reports. The user has the option of comparing performance data in the report against baseline data from a previous time period. Reports include such information as server availability, server resources, business performance, application performance, and database performance from the perspective of the application.
[0057] From the application programmer interface (API) and services provided by a specific application server (e.g., PMI in WebSphere) and the user's applications on which data collectors are operating, data are obtained. The obtained data will be a working set of data. A trend report, which is a selected type of report, may be obtained. Reports are stored on a server group level. Initially, data is obtained, such as from the API and server and the user's applications. The user may be able to determine the amount of application data to be captured. This amount may be expressed as a percentage of the total request samples that should be stored. The user is prompted to select the application server from which the request samples are taken. The user may be prompted to select the frequency, in terms of time periods, such as minutes, that the user wants the system to take a snapshot of the data. [0058] The use of redundant data should be limited. A sampling ratio is defined to determine how much of the data is to be recorded in a performance history database. The user is prompted to set the sampling ratio, thereby limiting the amount of data required for storage in the database. Table 1 shows the metrics, a description of each metric, and the resource from which the data is obtained.
Figure imgf000014_0001
Figure imgf000015_0001
[0059] Various types of reports may be provided, including a report type showing trends, and a decompose/decomposition report type on a single data point. [0060] In one embodiment, illustrated in Fig. 3, the user is prompted to provide certain data for the working set, as indicated at 305, and then provides those data, as indicated at 310. These data include the application server or group, the analysis type, the data period, the data interval, the aggregation period, i.e., the way in which the data is grouped, filtering criteria for selecting data points, the type of analysis, such as request, method, SQL, server availability, and application server analysis, and baseline. The user may then select a type of analysis, as indicated at 315. [0061] If request analysis has been selected, as indicated at 320, users are prompted to select a metric. Examples of metrics are throughput, response time, and CPU time, as indicated at 321. In response to the selection, a trend analysis is provided, with labels indicating the time interval and application server, as indicated at 322. Users may break down the request trend report by request type or request name, or by server name if the report applies to a server group. The foregoing breakdown may be referred to as a decomposition, as indicated at 323. Users may further break down any one portion of the decomposition. Alternatively, from the trend report, users may obtain details on any one data point. This further breakdown may be referred to as the detail report, as indicated at 324. The detail report may further be broken down into a trace report, indicated at 325, on one record of the detail report. The trace report provides method entry and exit information, as well as selected metrics. Thus it can be seen that the user can drill down to further levels of detail. [0062] If a method analysis is selected, as at 330, the user is prompted to select a metric, which maybe one of throughput, response time, and CPU time, as indicated at 331. The user is provided the option of limiting the report to such items as a specific request name, request type, or method name. After receiving the selection from the user, the system of the invention generates a report with a trend analysis, as indicated at 332. From the trend report, the user may select a breakdown of the trend analysis by request name or request type. The resulting report will be referred to as a decomposition report for method analysis, as indicated at 333. If applicable, users may decompose a trend analysis report by server, if the report covers a server group. Users may select any portion of the decomposition report for the method analysis for breakdown to detail and view by individual record, or users may select a breakdown of a single data point in the trend report into records. The resulting report is referred to as the detail report, indicated at 334.
[0063] If the user selects an SQL analysis report, as at 340, the user is prompted to select one of the metrics of throughput and response time, as at 341. Users may select a specific request name or request type, method name, table name, or SQL call. In response, the system provides a trend analysis, as at 342. The trend analysis may be broken down by request name, request type, method name, and/or table name to provide a decomposition report, as at 343. The report may include the number of samples as a percentage of total. Users may break down any one portion of the decomposition report to obtain detail by individual records, or break down the trend report by a single data point to obtain individual records. The report with individual records is known as the detail report, as at 344.
[0064] If the user selects a server availability analysis report, as at 350, a trend analysis is provided, as at 351. No metrics are selected. In a trend report for availability, the system may plot the percent up time of the group over a series of time intervals. The user may break down a trend report for a group by application server, as at 352.
[0065] An application server analysis report may be selected as at 360. The user may be prompted to provide one of the following metrics: pool size, concurrent waiters, average wait time, faults, percentage pool usage, physical connections, JVM free memory, and JVM memory used, as at 361. A trend analysis report is provided, as at 362.
[0066] Reports may be provided in any suitable manner. Trend reports may be a line graph, with a tablature view of all the data, for each data point. A comparative baseline display may be provided, showing the same data at a selected time past time. For example, baseline data may show the same data for the same time of day on a prior day. For decomposition reports, a bar or pie graph may be furnished, with a tablature view of all data, per type. The user is preferably able to select a portion of the decomposition report to drill down to a detail report. Baseline data may be provided in the detail report for comparison. Software Consistency Check
[0067] In a method, system and program of the invention, comparisons of the operation of applications on various servers may be conducted. Such comparisons are valuable in identifying possible configuration problems in different servers. [0068] An example of such a comparison is referred to as an n-way diff. As to each server, the program of the invention obtains runtime environment data as to how a system is set up and installed. These environments may be system, Java, and application server. For a system, the environment information may include CPU speed, number of CPUs online, number of CPUs offline, memory, operating system version, and physical disk space. Other information may be included. For Java, the information may include JDK version, installation directory, Java policy, operating system information, class path, and library path. For application servers, the information may include the application server, startup directory, listening ports, SSL listening ports, number of registered servlets, number of registered EJBs, number of JDBC connection pools, and number of EARs. The program can prompt a user to select a server as an authoritative server, as indicated in Fig. 4 at 405, receive a selection, as indicated at 410, and then prompt the user to select a server for comparison, as indicated at 415. Once the user selects the server for comparison, as indicated at 420, the system then obtains and displays the comparison results, as indicated at 425. The comparison results may include the runtime environment information noted above. The comparison results may contain only the differing data, and may be graphically represented. The system preferably permits a user to drill down from the displayed results to a detail screen displaying all of the relevant information for each application server, as indicated at 430, 435. [0069] In another type of comparison, comparison of binary files with matching file names can be performed. At a top level analysis, a user is prompted to select one server from a group as an authoritative server, as indicated at 505 in Fig. 5. The user provides a selection, as indicated at 510, and is then prompted to select one or more servers as comparison servers, as indicated at 515. Upon receipt of the comparison server(s) selection, at 520, the user is prompted to select the source of files, as at 525. The user may select from a list of EAR folders, or the CLASSPATH that is deemed to form the master file list of the authoritative server. The user provides the selection, as at 530. The user is also prompted, as at 535, to select one of the file types for the composition of the master file list. The file type is received, at 540. In response, the system starts preparing the master file list from the selected source and file types from the authoritative servers. The system then searches for files listed in the master file list in the comparison servers, as indicated at 545. For each comparison, the results are displayed, at 550. The results may be divided into found files and files not found. For the found category, the list includes matched files, i.e., all files with matched file name, size, and files system timestamp; like folders, i.e., files with matched file name and size, but not timestamp, and unlike folders, i.e., files.with matched file name only. For files not found, the files are divided into files in the authoritative server but not the comparison server, and all the files in the comparison server but not the authoritative server. These lists of files are displayed. This display permits the user to readily compare the files in the authoritative and comparison servers. [0070] From this display, the system permits the user to drill down to obtain additional information about the files. The user may select one comparison server, and select one file from the authoritative file, for detailed comparison, as indicated at 555. The system will perform a comparison on the files, with the result being either "same" or "different." The comparison may use a checksum calculation, such as the MD5 algorithm. It should be noted that, in one embodiment, a further level is required for JAR files before the comparison can be run. First, archive files are extracted, and then name matching is performed. Then the comparison may be run. As a result of these comparisons, both the names of the files and the contents of the files are compared between servers, as indicated at 560. Such problems as variant versions and corrupted code can readily be identified. Request Rewrite.
[0071] In a method, system, and program of the invention, a method, system and program may be provided for rewriting or mapping certain requests. In particular, three different types of requests are received in a system of the invention. These are JSPs, servlets, and remote Enterprise Java Bean calls. These requests are typically in the form of strings, and are received from another application, such as a web server or another application server. Such requests are employed in the system of the invention for two different purposes. The requests may be used for identification purposes. The requests may also be used to represent a business request or an application. In general, the implicit dual meanings of a request string are not problematic. However, there are situations in which these dual meanings can create conflicts. For example, in a portal site, request strings in the form of an URL normally look exactly the same, and therefore convenient for the end users to memorize; however, they are deemed to be different types of request by the portal engine using the underlying data object, such as a request or a session object. During problem determination, an operator or administrator will be confused as he will see requests for different functions represented by the same string, with no resolution between the strings. On the other hand, a single application may involve multiple and different request strings and after their successful executions, the resulting performance data is to be analyzed against one application name or label. The problem here again is that there is a lack of a group mechanism for the system to recognize that a group of request strings are related to each other.
[0072] To overcome the foregoing problems, a module, which may be in the form of Java based logic, may be provided to map requests. As indicated in Fig. 6, each request, such as request 600, is mapped to two separate strings: a distinguishable request string 605, and a collapsible request string 610. These separate strings are used for distinct purposes. These strings may be a distinct URL, or a label string. The mapping or rewriting operation preferably takes place at a point when both problem determination and performance management functions may take advantage of the operation. For example, performance management functions would perform decomposition by request on the collapsible request string. An active request search, used in problem determination, is conducted on distinguishable request strings.
Security.
[0073] Security is preferably maintained by providing that each user is assigned to a user role. Each user role is mapped to particular functions of the software of the invention. An access control list may be provided with the mapping between the product functions and the user roles associated with them. An administrator may add user roles and map those roles to functions. Referring to the schematic illustration in Fig. 7, and administrator 700 has read and write access to all functions and configurations, and access to log files. For example, creation, modification, activation, deactivation, and deletion of software traps, and changing of monitoring levels, may be for the administrator only. An operator 705 has display access to most functions, and access to certain function configuration. A user 710 has display access to functions and reports, but not to any function configuration.
Architecture
[0074] The system of the invention may have the architecture described below. The architecture may be in the nature of an agent operating on each application server, and the remaining components on a dedicated server, including a kernel providing central control, a publish server for receiving data from the probe engine, an archive agent for moving data from the cache to a database, a database, a visualization engine for providing all end user applications, and an application server agent for collecting certain application server specific data from an application server (such as Websphere). An exemplary architecture is illustrated at Fig. 8. Application server agents, such as one shown at 2510, are installed on application servers. Probe and publish engine 2511 is the principal component of application server agent 2510. The remaining components may be installed on dedicated server 2520. Kernel 2530 provides central control. Publish server 2540 receives data from application server agent 2510 and moves data to archive agent 2550. Archive agent 2550 moves data to database 2560. Visualization engine 2570 proves all end user applications, and communicates with the database for historical information, and directly with the application server agents 2510 to request and receive snapshot information. [0075] In one embodiment, the source of the data provided to the user in the method described above may be a probe and publish engine. The probe and publish engine obtains all information pertaining to specific threads. In a preferred embodiment, the standard Java profiling interface (JVMPI) may be employed for probe agents. [0076] Referring to Fig. 9, probe and publish engine 2511 is shown in relation to the Java virtual machine 2610 with which it communicates, as well as the application server 2615. Probe and publish engine 2511 preferably has five components: the probe controller 2512, command agent 2513, event agent 2514, event handlers 2515, and the publish engine 2516. Probe controller 2512 is a controller thread that controls the life cycle of the other components. Event agent 2514 registers the event handlers for JVMPI events of interest. When such events occur, the handlers are then invoked. The handlers collect the relevant information and add it to an event queue. Publish engine 2516 then obtains the data from the event queue and sends it to the publish server 2540. The agents may be constructed using the standard Java profiling interface provided with Java Development Kit 1.2.2 or above. [0077] In this embodiment, a JVMPI library is loaded with the JVM, and communicates with the JVM, the probe controller, the event agent, and the command agent. JNI functions may be used to capture all event-based data, and date/time stamp, wall clock and CPU clock. Events that are registered by the JVMPI library, event agent, command agent, publish engine, and probe controller, are shown at Table 2:
TABLE 2
Figure imgf000021_0001
Information obtained from the JVMPI library is stored in an queue, called the event queue, and the event agent retrieves records from the queue, packs them in a packet, and sends them to the publish server via the publish engine. The data collected from the queue by the Event Engine are shown at Table 3:
TABLE 3
Figure imgf000022_0001
The Command Agent is an RMI service registered with the kernel. The Command Agent receives commands from the visualization engine and other external components and satisfies them using JVMPI or JNI calls. An exemplary list of commands, and whether the commands are provided to the JVMPI or the JNI is shown at Table 4.
TABLE 4
Figure imgf000022_0002
[0078] The probe controller is also preferably an RMI service registered to kernel 2530, and starts and stops other probe components gets the probe's configuration. New configurations of probes are sent from kernel 2530 to the probe controller. The probe controller will determine if a probe should be started or stopped or a filter changed upon receiving a new configuration. A logic diagram for the Probe/Publish Engine is provided as Fig. 10. In accordance with this logic diagram, when the JVM is loaded, at shown at 2702, events identifying thread starts, thread end and completion of initialization of the JVM are registered through JVMPI to the kernel, as shown at 2704. When initialization of the JVM is completed, as indicated at 2706, then the system properties are set and a thread for initiating probes is created, as indicated at 2708. The thread then enables the method entry and class load events, as indicated at 2710, and waits until the application server has started, as shown at 2712. A method entry starts a process flow in the JVM, at 2714, which checks to see if the application server is started, at 2716. If it is started, the process flow is passed to the InitProbe Thread, which disables method entry and class load events, at 2718, and creates a probe controller thread, at 2720. The probe controller thread seeks a probe configuration from the kernel, at 2722. If the probe configuration is not found, then the flow ends, as indicated at 2724 and 2726. If the configuration is found, the process flow proceeds to determination if the probe is enabled in the configuration, at 2728. If not, then the process flow ends. A process flow may also commence with a new configuration in the form of an RMI call from the kernel, as indicated at 2730. If the probe is enabled, then the process flow proceeds to start the event agent and command agent, enable a class load events and a method entry events, as shown at 2732. The command agent awaits a command from the visualization engine, as indicated at 2734 and 2736. The enabling of the method entry event starts a process flow in the JVM, as indicated at 2750. Data, such as CPU clock, wall clock, method identification, thread identification, and/or URL and SQL are obtained, as indicated at 2750, and passed to event queue 2760. The class load event initiates a process flow in the JVM, as shown at 2754. A function of get class name, method name and signature is initiated, as shown at 2756, and this information is passed to class hash table 2762. The event agent retrieves records from the event queue 2760, as indicated at 2780. The event agent will wait depending on the publishing frequency, as indicated at 2782.
[0079] Visualization engine 2750 provides the front end user interface component used in the method and system of the invention. Standard J2EE technologies may be used for implementation of visualization engine 2750. The front-end framework of visualization engine 2750 handles housekeeping such as session management and security. The visualization engine 2750 preferably handles as many common tasks as possible in order to provide an environment conducive to the development of front- end application and business logic components. The visualization engine 2750 sits on top of a database, which it accesses in response to user requests. The architecture is illustrated at Fig. 28, and is shown to be browser-based, using a browser 2810, communicating with a web server 2815, which may be an Apache web server, and an application server 2820, such as IBM's Websphere, interfacing between the database and the web server. Servlets may be used to handle requests and manage application flow. Servlets may also be employed to control front-end behavior by performing form data-entry validation and sending java bean objects containing data to JSP pages. JSP pages may handle most of the front-end presentation logic. Business logic may be implemented using enterprise java beans Generally, stateless session beans are used.
[0080] Servlets may be used for form-entry data validation, as noted above, and for application logic flow. A base servlet may be provided that all servlet applications must extend. The base servlet sets up global variables, handles authentication and authorization, and performs redirects to login and access-denied pages as necessary. Resource bundle, log message and audit trail message files are provided. The JSP's generate HTML code to render the web page to be displayed in the browser. Servlets pass the desired data to the JSP's using java bean objects.
[0081] The top layer of the stateless session beans makes up the API. There may be a layer of enterprise java beans or java classes below the top layer that deals with access to data from the database. Data from the database may be obtained through a database access layer that is part of the DB Access data access framework. [0082] The application activity display function provides real-time access to data, as noted above, and involves direct communication between the visualization engine and the corresponding publish server and probes. A publish server interface and command agent interface are provided for this direct communication. The stubs to these interfaces are maintained by the kernel, and are retrieved by the visualization engine by performing a lookup from the kernel using a lookup agent helper client. Each server in which probes are running has a unique identification for the probe. Once the probe identification has been obtained, the interface stub of the command agent is obtained from the kernel. The identification of the publish server used by the probe is then obtained from the probe. The corresponding interface stub of the publish server is obtained from the kernel. The list of active requests and associated data can then be obtained directly from the selected publish server. Additional request data can be obtained from the probe directly. Communications between the visualization engine and the command agent and publish server of the probe are realtime and synchronous.
[0083] The visualization engine includes the security functions discussed above. A proprietary API was developed because the J2EE specification security features are not sufficient to provide the security features described above. Security features consist of authentication and authorization functions. Authentication is performed via a proprietary Java API that wraps a third party authentication system. Authorization is performed by maintaining access control lists by users or groups. A user is associated with specific groups and can only access data for servers in those groups. Servers are each associated with one or more groups.
[0084] The kernel will now be described in detail. The kernel enables various services to discover each other on a network and provides a way for services to interact in a dynamic, robust way. No user intervention is required when services are brought on or offline. Services that join the kernel can adapt dynamically when any of the other services go on or offline. Consumers of the services do not need prior knowledge of the service's implementation. Referring to Fig. , two instances of the kernel, 2530 and 2530', are shown. The architecture of the kernel features a core 2531, a lease administrator 2532, an RFS server 2533, a codebase server 2534, a registration database 2535, an availability server 2536, and a configuration server 2537. Two instances of the kernel are preferably running on separate servers for enhanced availability.
[0085] The kernel core 2531 handles all join, renew, leave and lookup requests from a service. The services are probe agents, the availability server 2536, and the configuration server 2537. For a join request, the service passes a proxy object and its associated service attributes to the kernel. The kernel fulfills the request by storing the proxy object and service attributes in the registration database. When a client needs a certain type of service to accomplish a task, it looks for the service by passing a search template and issuing a lookup request to the kernel. Based on the search template, the kernel will return the corresponding proxy object to the client. Each service is required to renew its lease by issuing a renew request to the kernel periodically. If the kernel does not receive a renew request when required, the kernel removes the service's proxy object and service attributes from the registration database. This renewal requirement avoids requests being sent to services that are unavailable. The probe and publish server preferably bundles the application and system information, such as the volume of completed requests and CPU utilization, when the lease is renewed. The lease concept thus serves to report the availability of the server and high-level statistical information. A service may also issue a leave request to the kernel.
[0086] The lease administrator component 2532 keeps track of the records in the registration database. If any registration is expired, or a leave request is received, the lease administrator 2532 causes the corresponding record to be removed so that the kernel will not pass the corresponding proxy object to any clients. The RFS (request for stub) server 2533 listens on a port for connections. When a connection is identified, a serialized stub object of the kernel is sent out to the service or client to use in interfacing with the kernel. The codebase server 2534 is similar to an HTTP server, but provides a facility to allow clients of a service to download the class definitions of the proxy object it obtains from the kernel. The registration database 2535 provides in-memory storage for proxy objects and associated service attributes. Server availability and statistical information resides in the registration database 2535. [0087] The availability server 2536 takes snapshots and stores the history of the registration database 2535 in order to facilitate providing availability of servers and statistical data to the visualization engine 2570.
[0088] The configuration server 2537 is a centralized place to store configuration data for all components. Configuration data is in XML form and is kept in the database. Users may change configuration through the visualization engine. When this is accomplished, the configuration server 2537 retrieves from the kernel a list of proxy objects that are adapting to the old configuration. The configuration server 2537 makes use of the proxy objects to broadcast the new configuration. This serves to update the configuration of probes in response to user commands at the visualization engine.
[0089] A helper utility, called JoinManager, requests the stub object of the kernel, and joins the kernel with the proxy object as well as its service attributes. If the stub object is not available, the utility will continue to retry until it succeeds. This utility also maintains and renews the lease. A lookup manager utility may be used by a client to look up a specific service. [0090] The publish server 2540 manages data received from the various publish engines. Multiple publish servers may be provided in a single installation. The publish server provides query capabilities for the visualization engines. The publish server also manages the incremental retrievals of performance management related data and system resources related data. The publish server architecture is shown at Fig. 13.
[0091] Publish server 2540 may be implemented as a multithreaded process. Each thread connects to a specific publish engine and receive data from it. It may also contain additional threads to deal with startup, shutdown and communications to the kernel.
[0092] Referring to Fig. 13, publish server 2540 spawns a thread to join the kernel, and regularly renews its contract, as shown at 3002. Publish server 2540 also spawns a thread to accept socket connections, as indicated at 3004. As indicated by decision block 3006, the next step depends on whether a query is received from the corresponding publish engine. If, rather than a query, data is received, a persistent socket connection is established, as indicated at 3008. The data is also associated with a request. Data is then obtained from the probe via the publish engine, as indicated at 3010. If a server restart signal is received, as indicated at 3012 and 3014, then the publish server resets the accumulated data for the restarted server before proceeding. If the data is from a new probe, as indicated at 3016 and 3018, then the server is registered so that the server's performance management related data and system resources related data will be retrieved periodically, such as every 5 minutes. The process flow then proceeds to processing the records, such as method level records, class load records, and GC records, received from the probe, as indicated at 3020. If a request is completed or there is no activity on the request for a certain amount of time, as indicated at 3022, then the request is removed from the active request list, as indicated at 3024. The process flow then returns to accept more data from the probe, as indicated by labeling leading from 3026. [0093] If the data is determined to be a query, then a property may be used to determine the appropriate type of information. Queries may ask for various information, as illustrated at 3030, 3032 and 3034. The result is then serialized and sent back to the publish engine. The publish server also receives certain administration requests made by its clients, such as for status, as indicated at 3036, and stop the service, as indicated at 3038. These tasks can be invoked by administrators. The connection is closed when the information in response to the query has been provided, as indicated at 3040, and the publish server becomes available to accept socket connections again.
[0094] It will be understood that the foregoing architecture represents one system having means for carrying out the steps of the method of the invention. The visualization engine comprises means for presenting information to a user, means for prompting a user, and means for receiving requests from a user. The probe engine comprises means for obtaining information regarding distributed applications, and for carrying out filtered monitoring of the distributed applications. It will be understood that the functions of the publish engine, archive, database and kernel cooperate with the visualization engine and the probe engine to provide one means for carrying out the steps of the method.
Self-Diagnosis
[0095] In a method, system and computer program of the invention, a method and system may be provided for conducting analysis of internal components of the architecture, and for reporting the results of the analysis to an operator. In an example, there may be provided views of the kernel, of the data collector component, of the publish server, and of the archive agent.
[0096] The kernel view indicates all running instances of the kernel component of a software system of the invention. For each instance, there is provided a kernel runtime environment detail and a component overview for each. Exemplary values in a kernel runtime environment detail include the platform, the D? address, various port numbers, a codebase library path, contract renewal interval, the start time, the file where the security policy is resident, driver names, and the URL of its corresponding database. The component overview may include the service name, the component identification, platform, D? address, the listen port number, the first join time, and the last contract renewal time. Each component identification in the component overview section may be a link to provide a corresponding view. For example, if a user clicks a link on component ID X, and its service name is data collector controller, the user is provided with the data collector component view. [0097] A data collector component view displays data pertaining to all up and running data collector controllers. There may be three sections in this view: Data collector controller runtime environment detail, data collector runtime environment detail, and publish server relationship. The first two sections provide configurations and environment in which the data collector controllers are running. The publish server relationship section displays the identity of the publish server to which the data collector is connecting. For the data collector controller runtime environment detail, the identities include component LD, the identity of the admin server, the identity of the application server, the identity of the platform, the D? address, a port number, a start time, the kernel codebase file location, the connected kernel, a configuration profile, whether or not the kernel is configured, and a security policy file. For the data collector runtime environment detail, the information is an identification number of the component, a port number, and whether the component is enabled. [0098] A publish server view provides information as to all up and running instances of the publish server component. For each instance, there may be four sections: publish server runtime environment detail, the data collector relationship, the PMI agent relationship, and the archive agent relationship.
[0099] An archive agent view shows all up and running instances of archive agent and for each instance of archive agent, there are two sections of information: the archive agent runtime environment detail, and the publish server relationship. The archive agent runtime environment detail lists the configuration and the environment of the archive agent. The publish server relationship information identifies the publish server that the archive agent is serving.
[00100] It will be understood that the foregoing provides real-time monitoring of the system of the invention, so that performance may be monitored and problems determined.
[00101] The system of the invention may be installed through installation of certain probe software on a server to be monitored, and a separate server for the remaining software of the invention. This configuration provides for relatively straightforward installation of the system of the invention. [00102] The present invention can be embodied in the form of methods and apparatus for practicing those methods. The present invention can also be embodied in the form of program code embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. The present invention can also be embodied in the form of program code, for example, whether stored in a storage medium, loaded into and/or executed by a machine, or transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via electromagnetic radiation, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. When implemented on a general-purpose processor, the program code segments combine with the processor to provide a unique device that operates analogously to specific logic circuits.
[00103] While the exemplary embodiments have been described with respect to enterprise applications using Java technologies, and specifically J2EE technologies, the methods of the invention may be implemented in other technologies. For example, the methods of the invention may be implemented in other platform- independent technologies. The methods of the invention may also be implemented in other technologies applicable to distributed enterprise applications.
[00104] While the invention has been described with reference to preferred embodiments, the invention should not be regarded as limited to preferred embodiments.

Claims

What is claimed is:
1. A method for monitoring the performance of applications running on a plurality of servers in a distributed computing environment, comprising the steps of: receiving from a user selected information for momtoring, momtoring application performance in accordance with the selected information, and making monitored performance information available to the user in accordance with the selected information.
2. The method of claim 1, wherein the user is prompted to identify a scope of information to be monitored, and wherein application server performance is monitored in accordance with the selected scope.
3. The method of claim 2, wherein said scope comprises a first momtoring level wherein the selected information comprises request level data and server level data.
4. The method of claim 3, wherein said scope further comprises a second momtoring level wherein the selected information further comprises API level data.
5. The method of claim 4, wherein said scope further comprises a third monitoring level, wherein the selected information further comprises method level data.
6. The method of claim 1, wherein the user is prompted to identify a schedule for monitoring of information, and wherein application server performance is monitored in accordance with the identified schedule.
7. A method for monitoring the performance of applications running on a plurality of servers in a distributed computing environment, comprising the steps of prompting a user to select a server or server group, a resource, and a threshold or condition for notification, comparing the value or quality of a parameter to the threshold or condition, and, if the parameter reaches the threshold or condition, logging information concerning the parameter.
8. The method of claim 7, further comprising the step of comparing the parameter to criteria for notifying a user, and notifying a user if the criteria are met.
9. The method of claim 7, wherein the threshold or condition is a value of a resource.
10. The method of claim 9, wherein the resource is a property of a method.
11. The method of claim 10, wherein the resource is CPU time.
12. The method of claim 7, wherein the threshold or condition is a number of hits.
13. The method of claim 12, wherein the resource is a request, and the condition is a string contained in the request.
14. The method of claim 7, wherein the resource relates to application server performance, and the condition is percentage of CPU time.
15. A method for monitoring the performance of applications running on a plurality of servers in a distributed computer system, comprising the steps of providing the user with performance information, receiving from the user a request for more specific performance information, and providing more detailed performance information.
16. The method of claim 15, further comprising the step of providing the user a selection of request analysis, method analysis, SQL analysis, server availability analysis, and application server analysis, and receiving a selection from the user.
17. The method of claim 16, further comprising the step of providing a trend analysis in accordance with the received selection.
18. The method of claim 17, further comprising the step of receiving a request for a decomposition report on a portion of the trend analysis, and providing a decomposition report.
19. The method of claim 18, further comprising the steps of receiving a request for a detail report on portion of the decomposition report, and providing a detail report.
20. A method for momtoring the performance of applications running on a plurality of servers in a distributed computer system, comprising the steps of receiving from the user an identification of a server as an authoritative server, another server as a comparison server, comparing runtime environment data and displaying a comparison.
21. The method of claim 20, wherein said runtime environment data is in the form of one or more of CPU data, server data and Java data between the selected servers.
22. The method of claim 21, wherein said CPU data comprises one or more of CPU speed, number of CPUs online, number of CPUs offline, memory, operating system version, and physical disk space.
23. The method of claim 21, wherein said server data comprises one or more of application server, startup directory, listening ports, SSL listening ports, number of registered servlets, number of registered EJBs, number of JDBC connection pools, and number of EARs.
24. The method of claim 21, wherein said Java data comprises one or more of JDK version, installation directory, Java policy, operating system information, class path, and library path.
25. A method for monitoring the performance of applications running on a plurality of servers in a distributed computer system, comprising the steps of receiving from the user an identification of a server as an authoritative server, and another server as a comparison server, and providing a list of matching and differing file names.
26. The method of claim 25, further comprising the step of comparing file size.
27. The method of claim 25, further comprising the step of comparing file time stamp.
28. The method of claim 25, further comprising the steps of receiving from the user a selection of a file, conducting a comparison of the files, and providing a result to the user.
29. The method of claim 28, wherein the step of conducting a comparison of the files further comprises conducting a comparison of the files via MD5 checksum calculation.
30. A method for monitoring the performance of applications running on a plurality of servers in a distributed computer system, comprising the steps of assigning a role to each user, and mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user.
31. The method of claim 30, wherein one of said assigned roles is administrator, said administrator having read/write access to each of the functions.
32. The method of claim 30, wherein one of said assigned roles is user, said user having display access only to each of the functions.
33. A method for processing of requests, comprising the steps of receiving a request string, and mapping the received request string to a distinguishable request string and a collapsible request string.
34. The method of claim 33, wherein the received request string is in the form of one of a JSP, a servlet, and remote Enterprise Java Bean calls.
35. The method of claim 33, further comprising the steps of prompting a user to create rules for mapping of a received request string to a distinguishable request string and a collapsible request string, receiving rules in response to the step of prompting, and applying the received rules.
36. A method for monitoring of performance of applications in a distributed environment, comprising the steps of providing, in a system running at least one application, a management application having various components for momtoring and management, and monitoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components.
37. A system for monitoring the performance of applications running on a plurality of servers in a distributed computing environment, comprising means for momtoring application performance in accordance with the selected information received from a user, and means for making monitored performance information available to the user in accordance with the selected information.
38. The system of claim 37, further comprising means for prompting a user to identify a scope of information to be monitored, and means for momtoring application server performance in accordance with the selected scope.
39. The system of claim 38, wherein said scope comprises a first momtoring level wherein the selected information comprises request level data and server level data.
40. The system of claim 39, wherein said scope further comprises a second momtoring level wherein the selected information further comprises API level data.
41. The system of claim 40, wherein said scope further comprises a third monitoring level, wherein the selected information further comprises method level data.
42. The system of claim 37, further comprising means for monitoring application server performance in accordance with an identified schedule received from a user.
43. A system for monitoring the performance of applications running on a plurality of servers in a distributed computing environment, comprising means for prompting a user to select a server or server group, a resource, and a threshold or condition for notification, means for comparing a value or quality of a parameter on the selected server or server group to the selected threshold or condition, and, means for logging information concerning the selected parameter if the selected parameter reaches the selected threshold or condition.
44. The system of claim 43, further comprising means for comparing the parameter to criteria for notifying a user, and means for notifying a user if the criteria are met.
45. The system of claim 43, wherein the threshold or condition is a value of a resource.
46. The system of claim 45, wherein the resource is a property of a method.
47. The system of claim 46, wherein the resource is CPU time.
48. The system of claim 43, wherein the threshold or condition is a number of hits.
49. The system of claim 48, wherein the resource is a request, and the condition is a string contained in the request.
50. The system of claim 43, wherein the resource relates to application server performance, and the condition is percentage of CPU time.
51. A system for monitoring the performance of applications running on a plurality of servers in a distributed computer system, comprising means for providing the user with performance information, and means for providing more detailed performance information in response to a user request for more detailed performance information.
52. The system of claim 51, further comprising means for providing the user a selection of request analysis, method analysis, SQL analysis, server availability analysis, and application server analysis, and means for receiving a selection from the user.
53. The system of claim 52, further comprising means for providing a trend analysis in accordance with the received selection.
54. The system of claim 53, further comprising means for receiving a request for a decomposition report on a portion of the trend analysis, and means for providing a decomposition report.
55. The system of claim 53, further comprising means for receiving a request for a detail report on portion of the decomposition report and means for providing a detail report.
56. A system for monitoring the performance of applications running on a plurality of servers in a distributed computer system, comprising means for receiving from the user an identification of a server as an authoritative server, another server as a comparison server, means for comparing runtime environment data and means for displaying a comparison.
57. The system of claim 56, wherein said runtime environment data is in the form of one or more of CPU data, server data and Java data between the selected servers.
58. The system of claim 57, wherein said CPU data comprises one or more of CPU speed, number of CPUs online, number of CPUs offline, memory, operating system version, and physical disk space.
59. The system of claim 57, wherein said server data comprises one or more of application server, startup directory, listening ports, SSL listening ports, number of registered servlets, number of registered EJBs, number of JDBC connection pools, and number of EARs.
60. The system of claim 57, wherein said Java data comprises one or more of JDK version, installation directory, Java policy, operating system information, class path, and library path.
61. A system for monitoring the performance of applications running on a plurality of servers in a distributed computer system, comprising means for, in response to a received identification of a first server as an authoritative server and second server as a comparison server, providing a list of matching and differing file names in said authoritative and comparison servers.
62. The system of claim 61, further comprising means for comparing file size.
63. The system of claim 61, further comprising means for file time stamps.
64. The system of claim 61, further comprising means for conducting a comparison of files selected by a user, and providing a result to the user.
65. The system of claim 64, wherein said means for conducting a comparison comprises means for conducting a comparison of the files via MD5 checksum calculation.
66. A system for monitoring the performance of applications running on a plurality of servers in a distributed computer system comprises means for assigning a role to each user, and means for mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user.
67. The system of claim 66, wherein one of said assigned roles is administrator, said administrator having read/write access to each of the functions.
68. The system of claim 66, wherein one of said assigned roles is user, said user having display access only to each of the functions.
69. A system for handling requests, comprising means for receiving a request string, and means for mapping the received request string to a distinguishable request string and a collapsible request string.
70. The system of claim 69, wherein the received request string is in the form of one of a JSP, a servlet, and a remote Enterprise Java Bean call.
71. The system claim 69, further comprising means for prompting a user to create rules for mapping of a received request string to a distinguishable request string and a collapsible request string, and means for applying rules received in response to a prompt to a user to create rules for mapping of a received request string to a distinguishable request string and a collapsible request string.
72. A system for monitoring of performance of applications in a distributed environment, comprising means for providing, in a system running at least one application, a management application having various components for momtoring and management, and means for momtoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components.
73. A computer program for monitoring the performance of applications running on a plurality of servers in a distributed computing environment, said program consisting of instructions stored on a medium, said instructions, when executed on a processor causing the processor to execute the steps of: receiving from a user selected information for monitoring, monitoring application performance in accordance with the selected information, and making monitored performance information available to the user in accordance with the selected information.
74. A computer program for monitoring the performance of applications running on a plurality of servers in a distributed computing environment, said program consisting of instructions stored on a medium, said instructions, when executed on a processor causing the processor to execute the steps of: prompting a user to select a server or server group, a resource, and a threshold or condition for notification, comparing the value or quality of a parameter to the threshold or condition, and, if the parameter reaches the threshold or condition, logging information concerning the parameter.
75. A computer program for monitoring the performance of applications running on a plurality of servers in a distributed computer system, said program consisting of instructions stored on a medium, said instructions, when executed on a processor causing the processor to execute the steps of: providing the user with performance information, receiving from the user a request for more specific performance information, and providing more detailed performance information.
76. A computer program for monitoring the performance of applications running on a plurality of servers in a distributed computer system, said program consisting of instructions stored on a medium, said instructions, when executed on a processor causing the processor to execute the steps of: receiving from the user an identification of a first server as an authoritative server, of a second server as a comparison server, comparing runtime environment data from said authoritative and comparison servers and displaying a comparison.
77. A computer program for monitoring the performance of applications mnning on a plurality of servers in a distributed computer system, said program consisting of instructions stored on a medium, said instructions, when executed on a processor causing the processor to execute the steps of: receiving from the user an identification of a first server as an authoritative server, and a second server as a comparison server, and providing a list of matching and differing file names on said authoritative and comparison servers.
78. A computer program for monitoring the performance of applications mnning on a plurality of servers in a distributed computer system, said program consisting of instructions stored on a medium, said instructions, when executed on a processor causing the processor to execute the steps of: assigning a role to each user, and mapping between access to functions and each user role by an access control list, whereby access to functions is limited depending on the assigned role of the user.
79. A computer program for processing of requests, said program consisting of instructions stored on a medium, said instructions, when executed on a processor causing the processor to execute the steps of: receiving a request string, and mapping the received request string to a distinguishable request string and a collapsible request string.
80. A computer program for monitoring of performance of applications in a distributed environment, comprising the steps of providing, in a system running at least one application, a management application having various components for monitoring and management, and momtoring and providing to a user in real-time information concerning configuration of the components and the relationships between the components.
PCT/US2003/020109 2002-06-25 2003-06-25 Method and system for monitoring performance of application in a distributed environment WO2004001555A2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP03742215A EP1527395A4 (en) 2002-06-25 2003-06-25 Method and system for monitoring performance of application in a distributed environment
JP2004516267A JP4528116B2 (en) 2002-06-25 2003-06-25 Method and system for monitoring application performance in a distributed environment
AU2003278862A AU2003278862A1 (en) 2002-06-25 2003-06-25 Method and system for monitoring performance of application in a distributed environment

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US39202202P 2002-06-25 2002-06-25
US60/392,022 2002-06-25

Publications (2)

Publication Number Publication Date
WO2004001555A2 true WO2004001555A2 (en) 2003-12-31
WO2004001555A3 WO2004001555A3 (en) 2005-03-03

Family

ID=30000796

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2003/020109 WO2004001555A2 (en) 2002-06-25 2003-06-25 Method and system for monitoring performance of application in a distributed environment

Country Status (7)

Country Link
US (5) US7870244B2 (en)
EP (1) EP1527395A4 (en)
JP (1) JP4528116B2 (en)
KR (1) KR100772999B1 (en)
CN (1) CN1662901A (en)
AU (1) AU2003278862A1 (en)
WO (1) WO2004001555A2 (en)

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1732002A1 (en) * 2005-06-10 2006-12-13 Sap Ag Calculating module runtimes on multiple platforms
US7194386B1 (en) 2005-10-17 2007-03-20 Microsoft Corporation Automated collection of information
WO2007048726A1 (en) * 2005-10-27 2007-05-03 International Business Machines Corporation Method and system for virtualized health monitoring of resources
KR100750834B1 (en) 2005-10-06 2007-08-22 (주)아이피엠에스 A method of data call stack tracing in data monitoring of JAVA byte code and a device for storing the method in compter program type
CN100385401C (en) * 2004-12-24 2008-04-30 富士通株式会社 Analysis technique of execution states in computer system
WO2010044797A1 (en) * 2008-10-16 2010-04-22 Hewlett-Packard Development Company, L.P. Performance analysis of applications
WO2010058523A1 (en) * 2008-11-20 2010-05-27 Hitachi, Ltd. Method of monitoring device forming information processing system, information apparatus and information processing system
WO2012092065A1 (en) * 2010-12-28 2012-07-05 Sevone, Inc. Scalable performance management system
WO2013132123A1 (en) 2012-03-08 2013-09-12 Consejo Superior De Investigaciones Científicas (Csic) Coating with photochromic properties, method for producing said coating and use thereof applicable to optical articles and glazed surfaces
US8744806B2 (en) 2008-10-29 2014-06-03 Sevone, Inc. Scalable performance management system
CN104182540B (en) * 2014-09-03 2017-10-27 北京国双科技有限公司 Index statistical information processing method and processing device in data warehouse
CN109726085A (en) * 2018-12-29 2019-05-07 云智慧(北京)科技有限公司 Method and system for tracking performance problem
WO2020094798A1 (en) 2018-11-08 2020-05-14 Samson Aktiengesellschaft Controlling access rights in a networked system with data processing
CN113064762A (en) * 2021-04-09 2021-07-02 上海新炬网络信息技术股份有限公司 Service self-recovery method based on multiple detection

Families Citing this family (224)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DK1239385T3 (en) * 2001-02-28 2003-10-20 Sap Ag Computer system for business applications with alert notification and conditional execution
CN100375013C (en) 2002-04-08 2008-03-12 国际商业机器公司 Method and system for problem determination in distributed enterprise applications
US7577951B2 (en) * 2002-05-30 2009-08-18 Hewlett-Packard Development Company, L.P. Performance of computer programs while they are running
JP4528116B2 (en) * 2002-06-25 2010-08-18 インターナショナル・ビジネス・マシーンズ・コーポレーション Method and system for monitoring application performance in a distributed environment
US7440464B2 (en) * 2002-08-29 2008-10-21 Nokia Corporation Server control plane connections recovery in a server-gateway architecture based telecommunication network
US7650403B2 (en) * 2002-11-20 2010-01-19 Microsoft Corporation System and method for client side monitoring of client server communications
US7734637B2 (en) * 2002-12-05 2010-06-08 Borland Software Corporation Method and system for automatic detection of monitoring data sources
US7529842B2 (en) * 2002-12-17 2009-05-05 International Business Machines Corporation Method, system and program product for detecting an operational risk of a node
US8443067B2 (en) * 2003-04-25 2013-05-14 Siemens Aktiengesellschaft Method and apparatus for identifying an order in a network
US20050033625A1 (en) * 2003-08-06 2005-02-10 International Business Machines Corporation Method, apparatus and program storage device for scheduling the performance of maintenance tasks to maintain a system environment
WO2005017715A2 (en) * 2003-08-15 2005-02-24 International Business Machines Corporation Method and system for monitoring performance of processes across multiple environments and servers
US20050076116A1 (en) * 2003-09-24 2005-04-07 Taiwan Semiconductor Manufacturing Co., Ltd. Information server performance alert system and method
US20050102429A1 (en) * 2003-11-06 2005-05-12 Sap Ag Portal cluster manager
WO2005048085A2 (en) 2003-11-13 2005-05-26 Commvault Systems, Inc. System and method for performing an image level snapshot and for restoring partial volume data
US7756968B1 (en) * 2003-12-30 2010-07-13 Sap Ag Method and system for employing a hierarchical monitor tree for monitoring system resources in a data processing environment
US7822826B1 (en) 2003-12-30 2010-10-26 Sap Ag Deployment of a web service
US7941521B1 (en) 2003-12-30 2011-05-10 Sap Ag Multi-service management architecture employed within a clustered node configuration
US7725572B1 (en) 2003-12-30 2010-05-25 Sap Ag Notification architecture and method employed within a clustered node configuration
US20050172029A1 (en) * 2004-01-29 2005-08-04 International Business Machines Corporation Method and apparatus for managing a connection pool using heuristic information
US7526550B2 (en) * 2004-03-26 2009-04-28 Sap Ag Unified logging service with a log viewer
US20050216510A1 (en) * 2004-03-26 2005-09-29 Reinhold Kautzleben System and method to provide a visual administrator in a network monitoring system
US7721266B2 (en) * 2004-03-26 2010-05-18 Sap Ag Unified logging service with a logging formatter
US8234374B2 (en) * 2004-04-26 2012-07-31 Microsoft Corporation Privacy model that grants access rights and provides security to shared content
US8073819B2 (en) * 2004-05-11 2011-12-06 At&T Intellectual Property I, L.P. System and method for storing element information
US7665063B1 (en) 2004-05-26 2010-02-16 Pegasystems, Inc. Integration of declarative rule-based processing with procedural programming
US7685575B1 (en) * 2004-06-08 2010-03-23 Sun Microsystems, Inc. Method and apparatus for analyzing an application
US7596546B2 (en) * 2004-06-14 2009-09-29 Matchett Douglas K Method and apparatus for organizing, visualizing and using measured or modeled system statistics
US7844969B2 (en) 2004-06-17 2010-11-30 Platform Computing Corporation Goal-oriented predictive scheduling in a grid environment
US7861246B2 (en) * 2004-06-17 2010-12-28 Platform Computing Corporation Job-centric scheduling in a grid environment
US7340654B2 (en) 2004-06-17 2008-03-04 Platform Computing Corporation Autonomic monitoring in a grid environment
US7761556B2 (en) * 2004-11-22 2010-07-20 International Business Machines Corporation Performance monitoring within an enterprise software system
US7788226B2 (en) * 2004-12-30 2010-08-31 Sap Ag Monitoring availability of applications
US7954062B2 (en) * 2005-01-03 2011-05-31 International Business Machines Corporation Application status board mitigation system and method
US7788497B2 (en) * 2005-01-13 2010-08-31 Bea Systems, Inc. Credential mapping of WebLogic and database user ids
US7769784B2 (en) * 2005-01-27 2010-08-03 International Business Machines Corporation System for autonomically improving performance of Enterprise Java Beans through dynamic workload management
US20060179428A1 (en) * 2005-02-10 2006-08-10 Kiyokuni Kawachiya Method and system for efficiently starting a JAVA application
US8856309B1 (en) * 2005-03-17 2014-10-07 Oracle America, Inc. Statistical tool for use in networked computer platforms
US7469362B2 (en) * 2005-04-15 2008-12-23 Microsoft Corporation Using a call stack hash to record the state of a process
GB0516554D0 (en) * 2005-08-11 2005-09-21 Ibm Method, apparatus and computer program for enabling monitoring of a resource
US7519024B2 (en) * 2005-08-17 2009-04-14 Sprint Communications Company Lp Resource selection in a communication network
US20070060367A1 (en) * 2005-09-14 2007-03-15 International Business Machines Corporation End-to-end transaction tracking in the enterprise
US20070064736A1 (en) * 2005-09-19 2007-03-22 Fujitsu Network Communications Zero suppressed performance management data interpretation and same value suppression and interpretation
US20070067369A1 (en) * 2005-09-22 2007-03-22 Minshall Robbie J Method and system for quantifying and comparing workload on an application server
US20070083525A1 (en) * 2005-10-11 2007-04-12 Rahul Srivastava JDBC debugging enhancements
US20070081464A1 (en) * 2005-10-11 2007-04-12 Fujitsu Network Communications, Inc. Real-time performance monitoring of ethernet data over sonet
US7823136B2 (en) * 2005-10-11 2010-10-26 Bea Systems, Inc. Callbacks for monitoring driver-level statistics
US20070083526A1 (en) * 2005-10-11 2007-04-12 Rahul Srivastava Monitoring statistics and profile information for JDBC resources
US7784033B2 (en) * 2005-10-11 2010-08-24 Bea Systems, Inc. JDBC monitoring and diagnostics enhancements
US7921084B2 (en) * 2005-10-11 2011-04-05 Oracle International Corporation Timer-driven diagnostic image inhibition for statement cache/connection pool
US8887241B2 (en) * 2006-02-22 2014-11-11 International Business Machines Corporation Virtual roles
US8924335B1 (en) 2006-03-30 2014-12-30 Pegasystems Inc. Rule-based user interface conformance methods
US20070266369A1 (en) * 2006-05-11 2007-11-15 Jiebo Guan Methods, systems and computer program products for retrieval of management information related to a computer network using an object-oriented model
US8166143B2 (en) * 2006-05-11 2012-04-24 Netiq Corporation Methods, systems and computer program products for invariant representation of computer network information technology (IT) managed resources
US20070294224A1 (en) * 2006-06-16 2007-12-20 Jean-Jacques Heler Tracking discrete elements of distributed transactions
US20070297337A1 (en) * 2006-06-21 2007-12-27 International Business Machines Corporation Apparatus and methods for determining availability and performance of entities providing services in a distributed system using filtered service consumer feedback
US7493302B2 (en) * 2006-06-26 2009-02-17 International Business Machines Corporation Federated transaction path and service level agreement monitoring across service oriented application partner domains
JP2008015648A (en) * 2006-07-04 2008-01-24 Yokogawa Electric Corp Application management framework
US8010849B2 (en) * 2006-09-05 2011-08-30 Arm Limited Diagnosing faults within programs being executed by virtual machines
US8281036B2 (en) 2006-09-19 2012-10-02 The Invention Science Fund I, Llc Using network access port linkages for data structure update decisions
US7752255B2 (en) * 2006-09-19 2010-07-06 The Invention Science Fund I, Inc Configuring software agent security remotely
US8627402B2 (en) 2006-09-19 2014-01-07 The Invention Science Fund I, Llc Evaluation systems and methods for coordinating software agents
US8607336B2 (en) * 2006-09-19 2013-12-10 The Invention Science Fund I, Llc Evaluation systems and methods for coordinating software agents
US8601530B2 (en) * 2006-09-19 2013-12-03 The Invention Science Fund I, Llc Evaluation systems and methods for coordinating software agents
US8055797B2 (en) * 2006-09-19 2011-11-08 The Invention Science Fund I, Llc Transmitting aggregated information arising from appnet information
US8224930B2 (en) * 2006-09-19 2012-07-17 The Invention Science Fund I, Llc Signaling partial service configuration changes in appnets
US8984579B2 (en) * 2006-09-19 2015-03-17 The Innovation Science Fund I, LLC Evaluation systems and methods for coordinating software agents
US8601104B2 (en) 2006-09-19 2013-12-03 The Invention Science Fund I, Llc Using network access port linkages for data structure update decisions
US20080072032A1 (en) * 2006-09-19 2008-03-20 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Configuring software agent security remotely
US9306975B2 (en) 2006-09-19 2016-04-05 The Invention Science Fund I, Llc Transmitting aggregated information arising from appnet information
US20080168311A1 (en) * 2007-01-08 2008-07-10 Microsoft Corporation Configuration debugging comparison
US20080172671A1 (en) * 2007-01-11 2008-07-17 International Business Machines Corporation Method and system for efficient management of resource utilization data in on-demand computing
US8250525B2 (en) * 2007-03-02 2012-08-21 Pegasystems Inc. Proactive performance management for multi-user enterprise software systems
WO2008127581A2 (en) * 2007-04-12 2008-10-23 Thomson Licensing Message mechanism for workflow interfacing
US9602340B2 (en) * 2007-04-20 2017-03-21 Sap Se Performance monitoring
US8898277B2 (en) * 2007-06-08 2014-11-25 Oracle International Corporation Performance monitoring infrastructure for distributed transaction service
WO2008153193A1 (en) * 2007-06-15 2008-12-18 Nec Corporation Address conversion device and address conversion method
US8874721B1 (en) * 2007-06-27 2014-10-28 Sprint Communications Company L.P. Service layer selection and display in a service network monitoring system
US10417586B2 (en) * 2007-08-31 2019-09-17 Red Hat, Inc. Attaching ownership to data
US7840653B1 (en) * 2007-10-25 2010-11-23 United Services Automobile Association (Usaa) Enhanced throttle management system
JP2009187542A (en) * 2008-01-10 2009-08-20 Nec Corp Request processing system, request processing method, and request processing program
US20090217259A1 (en) * 2008-02-26 2009-08-27 Microsoft Corporation Building Operating System Images Based on Applications
US7486196B1 (en) * 2008-04-14 2009-02-03 International Business Machines Corporation Using audio to detect changes to the performance of an application
JP2009294949A (en) * 2008-06-05 2009-12-17 Hitachi Ltd Storage device and method of measuring performance of the same
US20090319653A1 (en) * 2008-06-20 2009-12-24 International Business Machines Corporation Server configuration management method
US9477570B2 (en) * 2008-08-26 2016-10-25 Red Hat, Inc. Monitoring software provisioning
US9084937B2 (en) 2008-11-18 2015-07-21 Gtech Canada Ulc Faults and performance issue prediction
US8028196B2 (en) * 2008-11-18 2011-09-27 Gtech Corporation Predictive diagnostics and fault management
US8131842B1 (en) * 2009-02-11 2012-03-06 Charles Schwab & Co., Inc. System and method for collecting and displaying information about many computer systems
US8843435B1 (en) 2009-03-12 2014-09-23 Pegasystems Inc. Techniques for dynamic data processing
US8893156B2 (en) * 2009-03-24 2014-11-18 Microsoft Corporation Monitoring of distributed applications
US8468492B1 (en) 2009-03-30 2013-06-18 Pegasystems, Inc. System and method for creation and modification of software applications
US10157117B2 (en) * 2009-10-08 2018-12-18 International Business Machines Corporation Processing transaction timestamps
US8584123B2 (en) * 2009-10-08 2013-11-12 International Business Machines Corporation Linking transactions
US9117013B2 (en) 2009-10-08 2015-08-25 International Business Machines Corporation Combining monitoring techniques
US8316126B2 (en) 2009-10-08 2012-11-20 International Business Machines Corporation Stitching transactions
KR101136087B1 (en) * 2009-11-09 2012-04-17 서울대학교병원 Method and system for monitoring performance of application in a web environment
US9665461B2 (en) 2009-12-04 2017-05-30 Red Hat, Inc. Obtaining application performance data for different performance events via a unified channel
US8286192B2 (en) * 2009-12-04 2012-10-09 Red Hat, Inc. Kernel subsystem for handling performance counters and events
US8171340B2 (en) * 2009-12-11 2012-05-01 Red Hat, Inc. Software performance counters
US8935703B2 (en) * 2009-12-11 2015-01-13 Red Hat, Inc. Performance counter inheritance
US8954996B2 (en) * 2009-12-11 2015-02-10 Red Hat, Inc. Profiling the system providing performance statistics in real time
US8930525B2 (en) * 2010-04-27 2015-01-06 Hewlett-Packard Development Company, L.P. Method and apparatus for measuring business transaction performance
US9727322B2 (en) 2010-06-01 2017-08-08 Entit Software Llc Methods, apparatus, and articles of manufacture to deploy software applications
CN101968758B (en) * 2010-10-28 2012-10-10 西北工业大学 Multiple data point threshold detection method
US9378111B2 (en) * 2010-11-11 2016-06-28 Sap Se Method and system for easy correlation between monitored metrics and alerts
US8842119B2 (en) * 2010-11-17 2014-09-23 Hewlett-Packard Development Company, L.P. Displaying system performance information
US9467507B2 (en) * 2011-01-03 2016-10-11 Verizon Patent And Licensing Inc. Wireless network cloud computing resource management
US8909761B2 (en) * 2011-02-08 2014-12-09 BlueStripe Software, Inc. Methods and computer program products for monitoring and reporting performance of network applications executing in operating-system-level virtualization containers
US8880487B1 (en) 2011-02-18 2014-11-04 Pegasystems Inc. Systems and methods for distributed rules processing
US10140320B2 (en) 2011-02-28 2018-11-27 Sdl Inc. Systems, methods, and media for generating analytical data
US20120221319A1 (en) * 2011-02-28 2012-08-30 Andrew Trese Systems, Methods and Media for Translating Informational Content
EP2557503B1 (en) * 2011-07-28 2020-04-01 Tata Consultancy Services Ltd. Application performance measurement and reporting
RU2465635C1 (en) * 2011-08-02 2012-10-27 Открытое акционерное общество "ОТИК-групп" Method for diagnosing program-hardware environment for distributed computing in multicore single-chip systems during real-time problem solving using adaptive petri net graphs
US9984054B2 (en) 2011-08-24 2018-05-29 Sdl Inc. Web interface including the review and manipulation of a web document and utilizing permission based control
US20130073059A1 (en) * 2011-09-20 2013-03-21 Joseph Mark Brian User interface for determining resource consumption
US20130081001A1 (en) * 2011-09-23 2013-03-28 Microsoft Corporation Immediate delay tracker tool
US10270755B2 (en) 2011-10-03 2019-04-23 Verisign, Inc. Authenticated name resolution
US8874733B2 (en) 2011-12-14 2014-10-28 Microsoft Corporation Providing server performance decision support
US9195936B1 (en) 2011-12-30 2015-11-24 Pegasystems Inc. System and method for updating or modifying an application without manual coding
CN102567185B (en) * 2011-12-31 2014-11-12 北京新媒传信科技有限公司 Monitoring method of application server
US9413615B1 (en) * 2012-03-02 2016-08-09 Juniper Networks, Inc. Trap filtering within a device management protocol
US9298715B2 (en) 2012-03-07 2016-03-29 Commvault Systems, Inc. Data storage system utilizing proxy device for storage operations
US9471578B2 (en) 2012-03-07 2016-10-18 Commvault Systems, Inc. Data storage system utilizing proxy device for storage operations
US9471460B2 (en) 2012-03-29 2016-10-18 International Business Machines Corporation Characterization of real-time software base-station workloads at fine-grained time-scales
US9342537B2 (en) 2012-04-23 2016-05-17 Commvault Systems, Inc. Integrated snapshot interface for a data storage system
WO2013186870A1 (en) * 2012-06-13 2013-12-19 株式会社日立製作所 Service monitoring system and service monitoring method
US10382252B2 (en) * 2012-06-26 2019-08-13 Juniper Networks, Inc. Filtering within device management protocol queries
US9135135B2 (en) 2012-06-28 2015-09-15 Sap Se Method and system for auto-adjusting thresholds for efficient monitoring of system metrics
TW201405339A (en) * 2012-07-24 2014-02-01 Chunghwa Telecom Co Ltd Operation relationship linking module having web operations sharing with thread pool and JDBC pool
US9916306B2 (en) 2012-10-19 2018-03-13 Sdl Inc. Statistical linguistic analysis of source content
US9286185B2 (en) 2012-11-16 2016-03-15 Empire Technology Development Llc Monitoring a performance of a computing device
US9886346B2 (en) 2013-01-11 2018-02-06 Commvault Systems, Inc. Single snapshot for multiple agents
US20140025572A1 (en) * 2013-01-25 2014-01-23 Concurix Corporation Tracing as a Service
US9207969B2 (en) 2013-01-25 2015-12-08 Microsoft Technology Licensing, Llc Parallel tracing for performance and detail
US8954546B2 (en) 2013-01-25 2015-02-10 Concurix Corporation Tracing with a workload distributor
US9021262B2 (en) 2013-01-25 2015-04-28 Concurix Corporation Obfuscating trace data
US20130283281A1 (en) 2013-02-12 2013-10-24 Concurix Corporation Deploying Trace Objectives using Cost Analyses
US8924941B2 (en) 2013-02-12 2014-12-30 Concurix Corporation Optimization analysis using similar frequencies
US8997063B2 (en) 2013-02-12 2015-03-31 Concurix Corporation Periodicity optimization in an automated tracing system
US9436589B2 (en) 2013-03-15 2016-09-06 Microsoft Technology Licensing, Llc Increasing performance at runtime from trace data
US9223673B1 (en) 2013-04-08 2015-12-29 Amazon Technologies, Inc. Custom host errors definition service
US9575874B2 (en) 2013-04-20 2017-02-21 Microsoft Technology Licensing, Llc Error list and bug report analysis for configuring an application tracer
CN104142817B (en) * 2013-05-10 2017-08-22 中国电信股份有限公司 The method and apparatus of user resources usage amount is measured in Java applications
US9384115B2 (en) * 2013-05-21 2016-07-05 Amazon Technologies, Inc. Determining and monitoring performance capabilities of a computer resource service
CN104252391B (en) * 2013-06-28 2017-09-12 国际商业机器公司 Method and apparatus for managing multiple operations in distributed computing system
US10063450B2 (en) 2013-07-26 2018-08-28 Opentv, Inc. Measuring response trends in a digital television network
CN111522652B (en) * 2013-08-13 2024-02-13 英特尔公司 Power balancing for increased load density and improved energy efficiency
US9292415B2 (en) 2013-09-04 2016-03-22 Microsoft Technology Licensing, Llc Module specific tracing in a shared module environment
US9503341B2 (en) * 2013-09-20 2016-11-22 Microsoft Technology Licensing, Llc Dynamic discovery of applications, external dependencies, and relationships
US20150095015A1 (en) * 2013-09-27 2015-04-02 Statistics Solutions, Llc Method and System for Presenting Statistical Data in a Natural Language Format
US9772927B2 (en) 2013-11-13 2017-09-26 Microsoft Technology Licensing, Llc User interface for selecting tracing origins for aggregating classes of trace data
US9753812B2 (en) 2014-01-24 2017-09-05 Commvault Systems, Inc. Generating mapping information for single snapshot for multiple applications
US9639426B2 (en) * 2014-01-24 2017-05-02 Commvault Systems, Inc. Single snapshot for multiple applications
US9632874B2 (en) 2014-01-24 2017-04-25 Commvault Systems, Inc. Database application backup in single snapshot for multiple applications
US9495251B2 (en) 2014-01-24 2016-11-15 Commvault Systems, Inc. Snapshot readiness checking and reporting
US20170053222A1 (en) * 2014-02-19 2017-02-23 Hewlett Packard Enterprise Development Lp Role based assessment for an it management system
US9417970B2 (en) * 2014-02-27 2016-08-16 Halliburton Energy Services, Inc. Data file processing for a well job data archive
IN2014MU00819A (en) * 2014-03-11 2015-09-25 Tata Consultancy Services Ltd
US9280407B2 (en) 2014-04-16 2016-03-08 International Business Machines Corporation Program development in a distributed server environment
US9596164B1 (en) * 2014-06-26 2017-03-14 Juniper Networks, Inc. Application visibility in layer 3 networks
CN104156661A (en) * 2014-07-26 2014-11-19 珠海市君天电子科技有限公司 Device and method for preventing account passwords from being tampered
US9558093B2 (en) * 2014-07-30 2017-01-31 Microsoft Technology Licensing, Llc Visual tools for failure analysis in distributed systems
US9742690B2 (en) * 2014-08-20 2017-08-22 At&T Intellectual Property I, L.P. Load adaptation architecture framework for orchestrating and managing services in a cloud computing system
US10042716B2 (en) 2014-09-03 2018-08-07 Commvault Systems, Inc. Consolidated processing of storage-array commands using a forwarder media agent in conjunction with a snapshot-control media agent
US9774672B2 (en) 2014-09-03 2017-09-26 Commvault Systems, Inc. Consolidated processing of storage-array commands by a snapshot-control media agent
US10469396B2 (en) 2014-10-10 2019-11-05 Pegasystems, Inc. Event processing with enhanced throughput
US9648105B2 (en) 2014-11-14 2017-05-09 Commvault Systems, Inc. Unified snapshot storage management, using an enhanced storage manager and enhanced media agents
US9448731B2 (en) 2014-11-14 2016-09-20 Commvault Systems, Inc. Unified snapshot storage management
CN105988919B (en) * 2015-03-02 2018-12-25 阿里巴巴集团控股有限公司 Java type web container memory uses quantity measuring method and relevant apparatus
US10110688B2 (en) * 2015-03-20 2018-10-23 Sony Interactive Entertainment LLC System and method for remote monitoring of API performance and user behavior associated with user interface
US11283697B1 (en) 2015-03-24 2022-03-22 Vmware, Inc. Scalable real time metrics management
US10255081B2 (en) * 2015-07-17 2019-04-09 Accenture Global Solutions Limited Method and system for intelligent cloud planning and decommissioning
CN105138571B (en) * 2015-07-24 2019-12-24 四川长虹电器股份有限公司 Distributed file system and method for storing massive small files
US10313211B1 (en) * 2015-08-25 2019-06-04 Avi Networks Distributed network service risk monitoring and scoring
US10594562B1 (en) 2015-08-25 2020-03-17 Vmware, Inc. Intelligent autoscale of services
US10701136B1 (en) * 2015-08-26 2020-06-30 Amdocs Development Limited System, method, and computer program for monitoring application activity for a cluster of applications
US10044577B2 (en) * 2015-11-04 2018-08-07 International Business Machines Corporation Visualization of cyclical patterns in metric data
US9715721B2 (en) 2015-12-18 2017-07-25 Sony Corporation Focus detection
US11283900B2 (en) * 2016-02-08 2022-03-22 Microstrategy Incorporated Enterprise performance and capacity testing
US10440153B1 (en) 2016-02-08 2019-10-08 Microstrategy Incorporated Enterprise health score and data migration
US10212041B1 (en) 2016-03-04 2019-02-19 Avi Networks Traffic pattern detection and presentation in container-based cloud computing architecture
US10503753B2 (en) 2016-03-10 2019-12-10 Commvault Systems, Inc. Snapshot replication operations based on incremental block change tracking
US10931548B1 (en) 2016-03-28 2021-02-23 Vmware, Inc. Collecting health monitoring data pertaining to an application from a selected set of service engines
KR101955715B1 (en) * 2016-04-01 2019-03-07 한국전자통신연구원 Embedded system including a plurality of self-adaptive applications
US10698599B2 (en) 2016-06-03 2020-06-30 Pegasystems, Inc. Connecting graphical shapes using gestures
US10698647B2 (en) 2016-07-11 2020-06-30 Pegasystems Inc. Selective sharing for collaborative application usage
US10999240B1 (en) * 2016-08-31 2021-05-04 Verisign, Inc. Client controlled domain name service (DNS) resolution
US10574559B2 (en) 2016-11-10 2020-02-25 Bank Of America Corporation System for defining and implementing performance monitoring requirements for applications and hosted computing environment infrastructure
US10362110B1 (en) * 2016-12-08 2019-07-23 Amazon Technologies, Inc. Deployment of client data compute kernels in cloud
FR3061571B1 (en) * 2016-12-29 2019-04-19 Bull Sas METHOD AND SYSTEM FOR MONITORING BATCH PROCESSING OF APPLICATIONS EXECUTED IN A COMPUTER INFRASTRUCTURE
US10904211B2 (en) 2017-01-21 2021-01-26 Verisign, Inc. Systems, devices, and methods for generating a domain name using a user interface
US10348604B2 (en) 2017-02-01 2019-07-09 International Business Machines Corporation Monitoring a resource consumption of an application
CN107222331B (en) * 2017-04-26 2019-12-06 东软集团股份有限公司 method and device for monitoring performance of distributed application system, storage medium and equipment
US10644962B2 (en) * 2017-11-15 2020-05-05 APImetrics Inc. Continuous monitoring for performance evaluation of service interfaces
US10732885B2 (en) 2018-02-14 2020-08-04 Commvault Systems, Inc. Block-level live browsing and private writable snapshots using an ISCSI server
US10999168B1 (en) 2018-05-30 2021-05-04 Vmware, Inc. User defined custom metrics
US11048488B2 (en) 2018-08-14 2021-06-29 Pegasystems, Inc. Software code optimizer and method
CN109359019A (en) * 2018-08-15 2019-02-19 中国平安人寿保险股份有限公司 Application program capacity monitoring method, device, electronic equipment and storage medium
CN109298990B (en) * 2018-10-17 2023-04-14 平安科技(深圳)有限公司 Log storage method and device, computer equipment and storage medium
US11044180B2 (en) 2018-10-26 2021-06-22 Vmware, Inc. Collecting samples hierarchically in a datacenter
US11263111B2 (en) 2019-02-11 2022-03-01 Microstrategy Incorporated Validating software functionality
CN110209495B (en) * 2019-05-17 2023-08-18 上海新储集成电路有限公司 Method and system for adjusting operation environment
US11582120B2 (en) 2019-05-30 2023-02-14 Vmware, Inc. Partitioning health monitoring in a global server load balancing system
CN110245508A (en) * 2019-06-18 2019-09-17 广东电网有限责任公司 Localization method, device, equipment and the readable storage medium storing program for executing of database connection leakage
KR102072700B1 (en) * 2019-07-31 2020-02-03 (주)소울시스템즈 Apparatus and method for real-time application performance monitoring based on full packet processing
CN110601875B (en) * 2019-08-15 2022-08-19 平安普惠企业管理有限公司 Information output method, information output apparatus, management device, and computer-readable storage medium
US11106455B2 (en) 2019-08-15 2021-08-31 Microstrategy Incorporated Integration of containers with external elements
US11288053B2 (en) 2019-08-15 2022-03-29 Microstrategy Incorporated Conversion and restoration of computer environments to container-based implementations
US11637748B2 (en) 2019-08-28 2023-04-25 Microstrategy Incorporated Self-optimization of computing environments
US11210189B2 (en) 2019-08-30 2021-12-28 Microstrategy Incorporated Monitoring performance of computing systems
US11507295B2 (en) 2019-08-30 2022-11-22 Microstrategy Incorporated Backup, restoration, and migration of computer systems
US11354216B2 (en) 2019-09-18 2022-06-07 Microstrategy Incorporated Monitoring performance deviations
US11360881B2 (en) 2019-09-23 2022-06-14 Microstrategy Incorporated Customizing computer performance tests
US11438231B2 (en) 2019-09-25 2022-09-06 Microstrategy Incorporated Centralized platform management for computing environments
CN113055640B (en) * 2019-12-28 2023-06-20 浙江宇视科技有限公司 Method and device for managing equipment in monitoring system
US11093239B1 (en) 2020-05-13 2021-08-17 International Business Machines Corporation Application driven configuration of service management tools
US20210397620A1 (en) * 2020-06-19 2021-12-23 Clariti Cloud Inc. Configurable government process automation on multi tenant platform systems
US11567945B1 (en) 2020-08-27 2023-01-31 Pegasystems Inc. Customized digital content generation systems and methods
US11531613B1 (en) * 2021-03-19 2022-12-20 Headspin, Inc. Systems for remote determination of data from test devices
US20220369064A1 (en) * 2021-05-14 2022-11-17 Headspin, Inc. Systems for controlling acquisition of test data from devices
US11811861B2 (en) 2021-05-17 2023-11-07 Vmware, Inc. Dynamically updating load balancing criteria
US11799824B2 (en) 2021-06-14 2023-10-24 Vmware, Inc. Method and apparatus for enhanced client persistence in multi-site GSLB deployments
KR102368147B1 (en) * 2021-10-19 2022-02-25 강동원 Server monitoring system and the driving method
US11861342B2 (en) 2022-01-28 2024-01-02 Microstrategy Incorporated Enhanced cloud-computing environment deployment

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6633908B1 (en) * 1998-05-20 2003-10-14 International Business Machines Corporation Enabling application response measurement
US6658471B1 (en) * 2000-06-29 2003-12-02 International Business Machines Corporation Method and system for zero overhead software performance measurement instrumentation
US6701363B1 (en) * 2000-02-29 2004-03-02 International Business Machines Corporation Method, computer program product, and system for deriving web transaction performance metrics

Family Cites Families (71)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2626512B2 (en) 1993-11-02 1997-07-02 日本電気株式会社 Information processing performance measurement method
US5941947A (en) * 1995-08-18 1999-08-24 Microsoft Corporation System and method for controlling access to data entities in a computer network
US6119101A (en) 1996-01-17 2000-09-12 Personal Agents, Inc. Intelligent agents for electronic commerce
US5828833A (en) * 1996-08-15 1998-10-27 Electronic Data Systems Corporation Method and system for allowing remote procedure calls through a network firewall
US7146230B2 (en) 1996-08-23 2006-12-05 Fieldbus Foundation Integrated fieldbus data server architecture
US6438573B1 (en) 1996-10-09 2002-08-20 Iowa State University Research Foundation, Inc. Real-time programming method
US5870559A (en) * 1996-10-15 1999-02-09 Mercury Interactive Software system and associated methods for facilitating the analysis and management of web sites
US6031528A (en) * 1996-11-25 2000-02-29 Intel Corporation User based graphical computer network diagnostic tool
US6408336B1 (en) * 1997-03-10 2002-06-18 David S. Schneider Distributed administration of access to information
US5958010A (en) * 1997-03-20 1999-09-28 Firstsense Software, Inc. Systems and methods for monitoring distributed applications including an interface running in an operating system kernel
US6338150B1 (en) 1997-05-13 2002-01-08 Micron Technology, Inc. Diagnostic and managing distributed processor system
US6167537A (en) * 1997-09-22 2000-12-26 Hewlett-Packard Company Communications protocol for an automated testing system
US6014760A (en) * 1997-09-22 2000-01-11 Hewlett-Packard Company Scheduling method and apparatus for a distributed automated testing system
US6574661B1 (en) * 1997-09-26 2003-06-03 Mci Communications Corporation Integrated proxy interface for web based telecommunication toll-free network management using a network manager for downloading a call routing tree to client
JPH11120106A (en) * 1997-10-17 1999-04-30 Fujitsu Ltd Display system of server resource use state and storage medium for it
US6023696A (en) 1997-10-31 2000-02-08 Oracle Corporation Summary table query routing
US6070190A (en) 1998-05-11 2000-05-30 International Business Machines Corporation Client-based application availability and response monitoring and reporting for distributed computing environments
US6321263B1 (en) * 1998-05-11 2001-11-20 International Business Machines Corporation Client-based application availability
US6054987A (en) * 1998-05-29 2000-04-25 Hewlett-Packard Company Method of dynamically creating nodal views of a managed network
EP1103116B1 (en) 1998-08-03 2005-06-01 Firstsense Software, Inc. Method and program for monitoring distributed applications using diagnostic information
US6446028B1 (en) * 1998-11-25 2002-09-03 Keynote Systems, Inc. Method and apparatus for measuring the performance of a network based application program
US6360214B1 (en) 1998-12-16 2002-03-19 Microsoft Corporation Automatic database statistics creation
JP3190902B2 (en) * 1999-02-02 2001-07-23 中部日本電気ソフトウェア株式会社 Performance monitoring apparatus, performance monitoring method, and recording medium recording performance monitoring program
JP3265280B2 (en) 1999-02-18 2002-03-11 エヌイーシーソフト株式会社 Application performance analysis system
JP2000250833A (en) * 1999-02-26 2000-09-14 Hitachi Information Systems Ltd Operation information acquiring method for operation management of plural servers, and recording medium recorded with program therefor
JP2000315198A (en) * 1999-05-06 2000-11-14 Hitachi Ltd Distributed processing system and its performance monitoring method
DE60026788T2 (en) 1999-05-13 2006-10-12 Canon K.K. Device for searching a device in a network
US8862507B2 (en) 1999-06-14 2014-10-14 Integral Development Corporation System and method for conducting web-based financial transactions in capital markets
US7844594B1 (en) * 1999-06-18 2010-11-30 Surfwax, Inc. Information search, retrieval and distillation into knowledge objects
US6298451B1 (en) * 1999-11-02 2001-10-02 Idini Corporation Directory-based failure recovery and load balancing system
US6711739B1 (en) * 1999-11-08 2004-03-23 Sun Microsystems, Inc. System and method for handling threads of execution
US6829639B1 (en) 1999-11-15 2004-12-07 Netvision, Inc. Method and system for intelligent global event notification and control within a distributed computing environment
US6909481B2 (en) * 2000-11-07 2005-06-21 Seiko Epson Corporation Liquid crystal display and electronic appliance
EP1117220A1 (en) * 2000-01-14 2001-07-18 Sun Microsystems, Inc. Method and system for protocol conversion
US6453269B1 (en) * 2000-02-29 2002-09-17 Unisys Corporation Method of comparison for computer systems and apparatus therefor
US6691244B1 (en) 2000-03-14 2004-02-10 Sun Microsystems, Inc. System and method for comprehensive availability management in a high-availability computer system
CA2303739C (en) * 2000-04-04 2009-06-30 Webhancer Corporation Method and system for managing performance of data transfers for a data access system
US7415537B1 (en) * 2000-04-07 2008-08-19 International Business Machines Corporation Conversational portal for providing conversational browsing and multimedia broadcast on demand
US6892221B2 (en) * 2000-05-19 2005-05-10 Centerbeam Data backup
US7140022B2 (en) 2000-06-02 2006-11-21 Honeywell International Inc. Method and apparatus for slack stealing with dynamic threads
US7127743B1 (en) * 2000-06-23 2006-10-24 Netforensics, Inc. Comprehensive security structure platform for network managers
JP2002041331A (en) 2000-07-27 2002-02-08 Mitsubishi Electric Corp Server performance measuring device
JP2002082926A (en) 2000-09-06 2002-03-22 Nippon Telegr & Teleph Corp <Ntt> Distributed application test and operation management system
WO2002023337A2 (en) * 2000-09-12 2002-03-21 Falcon Asset Acquisition Group Method and apparatus for flash load balancing
JP2002099448A (en) 2000-09-21 2002-04-05 Ntt Data Corp Performance monitoring apparatus and its method
ATE381191T1 (en) * 2000-10-26 2007-12-15 Prismedia Networks Inc METHOD AND SYSTEM FOR MANAGING DISTRIBUTED CONTENT AND CORRESPONDING METADATA
US7937470B2 (en) * 2000-12-21 2011-05-03 Oracle International Corp. Methods of determining communications protocol latency
US7685224B2 (en) * 2001-01-11 2010-03-23 Truelocal Inc. Method for providing an attribute bounded network of computers
US7114163B2 (en) 2001-03-07 2006-09-26 Hardin David S Software component model for time sensitive embedded applications
US6616049B1 (en) * 2001-04-10 2003-09-09 Symbol Technologies, Inc. Retail sales customer marketing system with electronic coupon processing
US7051339B2 (en) * 2001-06-29 2006-05-23 Goldman, Sachs & Co. System and method to measure latency of transaction information flowing through a computer system
US6976193B2 (en) * 2001-09-20 2005-12-13 Intel Corporation Method for running diagnostic utilities in a multi-threaded operating system environment
US20030065764A1 (en) 2001-09-26 2003-04-03 Karen Capers Integrated diagnostic center
US6941298B2 (en) 2002-01-18 2005-09-06 Bea Systems, Inc. System and method for providing result sets using EJB query language
US20030195875A1 (en) * 2002-03-25 2003-10-16 Valk Jeffrey W. Information management structure
CN100375013C (en) 2002-04-08 2008-03-12 国际商业机器公司 Method and system for problem determination in distributed enterprise applications
US8234128B2 (en) * 2002-04-30 2012-07-31 Baxter International, Inc. System and method for verifying medical device operational parameters
JP4528116B2 (en) * 2002-06-25 2010-08-18 インターナショナル・ビジネス・マシーンズ・コーポレーション Method and system for monitoring application performance in a distributed environment
US7945909B2 (en) * 2003-05-09 2011-05-17 Sap Aktiengesellschaft Initiating recovery of an executing task using historical information and task information
WO2005017715A2 (en) * 2003-08-15 2005-02-24 International Business Machines Corporation Method and system for monitoring performance of processes across multiple environments and servers
US7725529B2 (en) * 2003-11-19 2010-05-25 George Mason Intellectual Properties, Inc. Geographic information system
US20060167929A1 (en) * 2005-01-25 2006-07-27 Amit Chakraborty Method for optimizing archival of XML documents
US7757214B1 (en) * 2005-11-10 2010-07-13 Symantec Operating Coporation Automated concurrency configuration of multi-threaded programs
EP1949273A1 (en) * 2005-11-16 2008-07-30 Evri Inc. Extending keyword searching to syntactically and semantically annotated data
US7650394B2 (en) * 2006-09-15 2010-01-19 Microsoft Corporation Synchronizing email recipient lists using block partition information
US7945804B2 (en) * 2007-10-17 2011-05-17 International Business Machines Corporation Methods and systems for digitally controlled multi-frequency clocking of multi-core processors
US8443056B2 (en) * 2010-01-22 2013-05-14 Netflix, Inc. Client-server signaling in content distribution networks
US8341650B1 (en) * 2010-02-02 2012-12-25 Cellco Partnership High thread count analyzer for web application server environment
JP5730518B2 (en) * 2010-08-27 2015-06-10 株式会社日立国際電気 Specific person detection system and specific person detection method
US20120324568A1 (en) * 2011-06-14 2012-12-20 Lookout, Inc., A California Corporation Mobile web protection
US8738765B2 (en) * 2011-06-14 2014-05-27 Lookout, Inc. Mobile device DNS optimization

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6633908B1 (en) * 1998-05-20 2003-10-14 International Business Machines Corporation Enabling application response measurement
US6701363B1 (en) * 2000-02-29 2004-03-02 International Business Machines Corporation Method, computer program product, and system for deriving web transaction performance metrics
US6658471B1 (en) * 2000-06-29 2003-12-02 International Business Machines Corporation Method and system for zero overhead software performance measurement instrumentation

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1527395A2 *

Cited By (23)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100385401C (en) * 2004-12-24 2008-04-30 富士通株式会社 Analysis technique of execution states in computer system
EP1732002A1 (en) * 2005-06-10 2006-12-13 Sap Ag Calculating module runtimes on multiple platforms
KR100750834B1 (en) 2005-10-06 2007-08-22 (주)아이피엠에스 A method of data call stack tracing in data monitoring of JAVA byte code and a device for storing the method in compter program type
US7472040B2 (en) 2005-10-17 2008-12-30 Microsoft Corporation Automated collection of information
US7194386B1 (en) 2005-10-17 2007-03-20 Microsoft Corporation Automated collection of information
CN101297272B (en) * 2005-10-27 2012-05-09 国际商业机器公司 Method and system for virtualized health monitoring of resources
US8095641B2 (en) 2005-10-27 2012-01-10 International Business Machines Corporation Method and system for virtualized health monitoring of resources
WO2007048726A1 (en) * 2005-10-27 2007-05-03 International Business Machines Corporation Method and system for virtualized health monitoring of resources
US8635498B2 (en) 2008-10-16 2014-01-21 Hewlett-Packard Development Company, L.P. Performance analysis of applications
WO2010044797A1 (en) * 2008-10-16 2010-04-22 Hewlett-Packard Development Company, L.P. Performance analysis of applications
US8744806B2 (en) 2008-10-29 2014-06-03 Sevone, Inc. Scalable performance management system
US8225011B2 (en) 2008-11-20 2012-07-17 Hitachi, Ltd. Method of monitoring device forming information processing system, information apparatus and information processing system
US8024494B2 (en) 2008-11-20 2011-09-20 Hitachi, Ltd. Method of monitoring device forming information processing system, information apparatus and information processing system
WO2010058523A1 (en) * 2008-11-20 2010-05-27 Hitachi, Ltd. Method of monitoring device forming information processing system, information apparatus and information processing system
WO2012092065A1 (en) * 2010-12-28 2012-07-05 Sevone, Inc. Scalable performance management system
US9009185B2 (en) 2010-12-28 2015-04-14 Sevone, Inc. Scalable performance management system
WO2013132123A1 (en) 2012-03-08 2013-09-12 Consejo Superior De Investigaciones Científicas (Csic) Coating with photochromic properties, method for producing said coating and use thereof applicable to optical articles and glazed surfaces
CN104182540B (en) * 2014-09-03 2017-10-27 北京国双科技有限公司 Index statistical information processing method and processing device in data warehouse
WO2020094798A1 (en) 2018-11-08 2020-05-14 Samson Aktiengesellschaft Controlling access rights in a networked system with data processing
DE102018127949A1 (en) 2018-11-08 2020-05-14 Samson Aktiengesellschaft Control of access rights in a networked system with data processing
CN109726085A (en) * 2018-12-29 2019-05-07 云智慧(北京)科技有限公司 Method and system for tracking performance problem
CN113064762A (en) * 2021-04-09 2021-07-02 上海新炬网络信息技术股份有限公司 Service self-recovery method based on multiple detection
CN113064762B (en) * 2021-04-09 2024-02-23 上海新炬网络信息技术股份有限公司 Service self-recovery method based on various detection

Also Published As

Publication number Publication date
US9053220B2 (en) 2015-06-09
US20040064552A1 (en) 2004-04-01
AU2003278862A8 (en) 2004-01-06
WO2004001555A3 (en) 2005-03-03
US20090019441A1 (en) 2009-01-15
JP2005531070A (en) 2005-10-13
KR100772999B1 (en) 2007-11-05
EP1527395A4 (en) 2006-03-01
JP4528116B2 (en) 2010-08-18
US9678964B2 (en) 2017-06-13
KR20060066570A (en) 2006-06-16
US20150234816A1 (en) 2015-08-20
CN1662901A (en) 2005-08-31
US7870244B2 (en) 2011-01-11
US20090070462A1 (en) 2009-03-12
US20110276594A1 (en) 2011-11-10
EP1527395A2 (en) 2005-05-04
AU2003278862A1 (en) 2004-01-06
US8037205B2 (en) 2011-10-11

Similar Documents

Publication Publication Date Title
US9678964B2 (en) Method, system, and computer program for monitoring performance of applications in a distributed environment
US9727405B2 (en) Problem determination in distributed enterprise applications
US6122664A (en) Process for monitoring a plurality of object types of a plurality of nodes from a management node in a data processing system by distributing configured agents
US7167915B2 (en) Monitoring storage resources used by computer applications distributed across a network
JP5148607B2 (en) Automation of standard operating procedures in database management
US20050066027A1 (en) Method of displaying events
US20060047805A1 (en) Apparatus, system, and method for gathering trace data indicative of resource activity
WO2007036932A2 (en) Data table management system and methods useful therefor
WO2007048653A2 (en) A method and system for systems management tasks on endpoints
JP2002522957A (en) System and method for monitoring a distributed application using diagnostic information
US20050022209A1 (en) Distributed computer monitoring system and methods for autonomous computer management
US20030084071A1 (en) Method and system for managing computer performance
Malcher et al. Database Troubleshooting
Malcher et al. Automation and Troubleshooting
Phelps et al. Monitoring and Troubleshooting
Alapati et al. Analyzing Operating System Performance
Jamen et al. Oracle Fusion Middleware Performance and Tuning Guide 11g Release 1 (11.1. 1.7. 0) E10108-13
Jamen Oracle Fusion Middleware Performance and Tuning Guide 11g Release 1 (11.1. 1) E10108-06
Strasser Long-term workload monitoring: workload management on distributed OS/2 server systems
Jamen Oracle Fusion Middleware Performance and Tuning Guide 11g Release 2 (11.1. 2) E28552-02

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2003742215

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 2004516267

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 20038148773

Country of ref document: CN

WWE Wipo information: entry into national phase

Ref document number: 1020047021335

Country of ref document: KR

WWP Wipo information: published in national office

Ref document number: 2003742215

Country of ref document: EP

DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWW Wipo information: withdrawn in national office

Ref document number: 2003742215

Country of ref document: EP