WO2001016753A2 - Post-deployment monitoring of server performance - Google Patents

Post-deployment monitoring of server performance Download PDF

Info

Publication number
WO2001016753A2
WO2001016753A2 PCT/US2000/024303 US0024303W WO0116753A2 WO 2001016753 A2 WO2001016753 A2 WO 2001016753A2 US 0024303 W US0024303 W US 0024303W WO 0116753 A2 WO0116753 A2 WO 0116753A2
Authority
WO
WIPO (PCT)
Prior art keywords
computers
server
transactional server
computer
agent
Prior art date
Application number
PCT/US2000/024303
Other languages
French (fr)
Other versions
WO2001016753A3 (en
Inventor
Amnon Landan
Original Assignee
Mercury Interactive 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 Mercury Interactive Corporation filed Critical Mercury Interactive Corporation
Priority to EP00959879A priority Critical patent/EP1214657A2/en
Priority to JP2001520640A priority patent/JP2003508849A/en
Priority to CA002380358A priority patent/CA2380358A1/en
Priority to AU71123/00A priority patent/AU763468B2/en
Publication of WO2001016753A2 publication Critical patent/WO2001016753A2/en
Publication of WO2001016753A3 publication Critical patent/WO2001016753A3/en

Links

Classifications

    • 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
    • G06F11/3414Workload generation, e.g. scripts, playback
    • 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/323Visualisation of programs or trace data
    • 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/327Alarm or error message 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
    • 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/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
    • G06F11/3419Recording 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 by assessing time
    • 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
    • G06F2201/00Indexing scheme relating to error detection, to error correction, and to monitoring
    • G06F2201/875Monitoring of systems including the internet

Definitions

  • the present invention relates to software tools for testing and monitoring the operation of web-based and other transactional servers.
  • a user can record or otherwise create a test script which specifies a sequence of user interactions with the transactional server.
  • the user may also optionally specify certain expected responses from the transactional server, which may be added to the test script as verification points.
  • the user may record a session with a web-based travel reservation system during which the user searches for a particular flight, and may then define one or more verification points to check for an expected flight number, departure time or ticket price.
  • Test scripts generated through this process are "played” or “executed” to simulate the actions of users - typically prior to deployment of the component being tested.
  • the testing tool monitors the performance of the transactional server, including determining the pass/fail status of any verification points. Multiple test scripts may be replayed concurrently to simulate the load of a large number of users.
  • Using an automation interface of the LoadRunner product it is possible to dispatch test scripts to remote computers for execution.
  • the results of the test are typically communicated to the user through a series of reports that are accessible through the user interface of the testing tool.
  • the reports may contain, for example, graphs or charts of the observed response times for various types of transactions. Performance problems discovered through the testing process may be corrected by programmers or system administrators.
  • a variety of tools and services also exist that allow web site operators to monitor the post-deployment performance of their web sites. For example, Keynote Systems Inc. of San Mateo California provides a service which uses automated agents to access a web site at regular intervals throughout the day.
  • the agents computers which are provided by Keynote Systems in selected major cities, measure the time required to perform various web site functions, and report the results to a server provided by Keynote Systems.
  • the owner or operator of the web site can access this server using a web browser to view the collected performance data on a city-b ⁇ -cit ⁇ or other basis.
  • Other types of existing monitoring tools include log analysis tools that process access logs generated by web servers, and packet sniffing tools that monitor traffic to and from the web server. Summary of the Invention A significant problem with existing monitoring tools and services is that they often fail to detect problems that are dependent upon the attributes of typical end users, such as the user's location, PC configuration, ISP (Internet Service Provider), or Internet router.
  • the web site operator can monitor the web site only from the agent computers and locations made available by the service provider; as a result, the service may not detect a performance problem seen by the most frequent users of the system (e.g., members of a customer service department who access the web site through a particular ISP, or who use a particular PC configuration).
  • a monitoring service may indicate that web site users in a particular city are experiencing long delays, but may fail to reveal that the problem is experienced only by users that access the site through a particular router. Without such additional information, system administrators may not be able to isolate and correct such problems.
  • the present invention addresses these and other problems by providing a software system and method for monitoring the post-deployment operation of a web site system or other transactional server.
  • the system includes an agent component ("agent") which simulates the actions of actual users of the transactional server while monitoring and reporting the server's performance.
  • agent is adapted to be installed on selected computers ("agent computers") to be used for monitoring, including computers of actual end users.
  • agents computers can be remotely programmed (typically by the operator of the transactional server) using a controller component (“controller").
  • the controller provides a user interface and various functions for a user to remotely select the agent computer(s) to include in a monitoring session, assign attributes to such computers (such as the location, organization, ISP and/or configuration of each computer), and assign transactions and execution schedules to such computers
  • the execution schedules may be periodic or repetitive schedules, (e.g., every hour, Monday through Friday), so that the transactional server is monitored on a continuous or near-continuous basis.
  • the controller preferably represents the monitoring session on the display screen as an expandable tree in which the transactions and execution schedules are represented as children of the corresponding computers. Once a monitoring session has been defined, the controller dispatches the transactions and execution schedules to the respective agent computers over the Internet or other network.
  • the controller also preferably includes functions for the user to record and edit transactions, and to define alert conditions for generating real-time alert notifications.
  • the controller may optionally be implemented as a hosted application on an Internet or intranet site, in which case users may be able to remotely set up monitoring sessions using an ordinary web browser.
  • each agent computer executes its assigned transactions according to its assigned execution schedule, and generates performance data that indicates one or more characteristics of the transactional server's performance.
  • the performance data may include, for example, the server response time and pass/fail status of each transaction execution event.
  • the pass/fail status values may be based on verification points
  • the agent computers preferably report the performance data associated with a transaction immediately after transaction execution, so that the performance data is available substantially in real time for viewing and generation of alert notifications.
  • the performance data generated by the various agent computers is aggregated in a centralized database which is remotely accessible through a web-based reports server.
  • the reports server provides various user-configurable charts and graphs that allow the operator of the transactional server to view the performance data associated with each transaction.
  • the reports server generates reports which indicate the performance of the transactional server separately for the various operator-specified attributes.
  • the user can, for example, view and compare the performance of the transactional server as seen from different operator-specified locations (e.g., New York, San Francisco, and U.K.), organizations (e.g., accounting, marketing, and customer service departments), ISPs (e.g., Spring, AOL and Earthlink), or other attribute type.
  • the user may also have the option to filter out data associated with particular attributes and/or transactions (e.g., exclude data associated with AOL customers), and to define new attribute types (e.g., modem speed or operating system) for partitioning the performance data.
  • the ability to monitor the performance data according to the operator specified attributes greatly facilitates the task of isolating and correcting attribute-dependant performance problems.
  • the performance data is monitored substantially in real time (preferably by the controller) to check for any user defined alert conditions.
  • a notification message may be sent by email, pager, or other communications method to an approp ⁇ ate person.
  • the alert conditions may optionally be specific to a particular location, organization, ISP, or other attribute.
  • a system administrator responsible for an Atlanta branch office may request to be notified when a particular problem (e.g., average response time exceeds a particular threshold) is detected by computers in that office
  • a particular problem e.g., average response time exceeds a particular threshold
  • the administrator can use a standard web browser to access the reports server and view the details of the event or events that triggered the notification.
  • the agent computers may be programmed to capture sequences of screen displays during transaction execution, and to transmit these screen displays to the reports server for viewing when a transaction fails.
  • an agent computer may be programmed to launch a network monitor component when the path delay between the agent computer and the transactional server exceeds a preprogrammed threshold. Upon being launched, the network monitor component determines the delays currently being experienced along each segment of the network path The measured segment delays are reported to personnel (preferably through the reports server), and may be used to detect various types of network problems.
  • one or more of the agent computers may be remotely programmed to scan or crawl the monitored web site periodically to check for broken links (links to inaccessible objects). When broken links are detected, they may be reported by email, through the reports server, or by other means.
  • Figure 1 illustrates the general architecture of the monitoring tool, and illustrates how the monitoring tool may be used to monitor the performance of a web based transactional server.
  • Figure 2 illustrates a main user interface screen of the controller depicted in Figure 1.
  • Figures 3 9 illustrate the controller's Setup Wizard screens that are used to set up monitoring sessions,
  • Figures 10 12 illustrate screens of the controller's Alerts Wizard
  • Figure 13 16 illustrate example status report web pages provided by the web reports server in Figure 1, with Figure 14 illustrating a representative "drill down" page returned when the user selects the drill down link in Figure 13 for the "browse order status" transaction.
  • Figures 17 19 are flow diagrams that illustrate the flow of information between components during the setup and execution of a monitoring session.
  • Figure 20 illustrates a process for capturing screen displays on failed transactions.
  • Detailed Description of the Preferred Embodiment The following description sets forth numerous implementation-specific details of a distributed monitoring tool and associated methods. These details are provided in order to illustrate a preferred embodiment of the invention, and not to limit the scope of the invention. The scope of the invention is defined only by the appended claims
  • the transactional server being monitored is a web based system that is accessible via the Internet. It will be recogmzed, however, that the inventive methods can also be used to monitor other types of transactional servers, including those that use proprietary protocols or are accessible only to internal users of a particular organization. For example, the underlying methodology can also be used to monitor internal intranets, two-tier client/server systems, SAP R/3 systems, and other types of distributed systems.
  • Figure 1 illustrates the general components of the distributed monitoring tool, and illustrates how these components may be deployed within a network to test and monitor a web based transactional server 30. Dashed lines in Figure 1 indicate typical machine boundaries, with open boxes indicating one or more machines.
  • the transactional server 30 typically includes a web server component 30A and one or more applications 30B
  • the applications may, for example, provide functionality for implementing one or more business processes, such as setting up a user account or placing an order.
  • the applications 30B typically provide user access to one or more back end databases (not shown).
  • the transactional server may include multiple machines, including machines that are geographically remote from one another.
  • the monitoring tool consists of three primary software components: an agent 32, a controller 34 and a web based reports server 36.
  • Each component 32, 34, 36 includes one or more executable files or modules stored within a computer-readable medium.
  • the agent 32 includes the basic functionality for simulating the actions of users of the transactional server
  • the agent 32 is preferably installed on multiple Internet-connected host computers 40 (PCs, workstations, etc.) so that the end user experience can be captured from multiple locations.
  • host computers 40 may advantageously include computers that are owned or controlled by the operator of the transactional server 30.
  • the operator of the transactional server can install the agent component on selected computers within each of the departments or organizations from which the transactional server is frequently accessed, including computers of actual end users.
  • the computers 40 that host the agent 32 will be referred to as “agent computers,” and a computer 35 that hosts the controller 34 will be referred to as a “controller computer.” It should be understood, however, that a single computer could host two or more of the tool's components 32, 34, and 36, and that the functionality of the monitoring tool could be divided differently between components.
  • the web reports server 36 and the transactional server 30 could be accessed through a common web site.
  • the controller 34 provides a user interface (Ul) through which the operator of the transactional server can set up and initiate monitoring sessions, including distributed monitoring sessions in which the transactional server is accessed and monitored from multiple user locations. Through this Ul, the user can, among other things, select the agent computers 40 to be included within a monitoring session, and assign transactions and execution schedules to such computers.
  • the controller 34 also provides functions for specifying alert conditions, and for notifying personnel when such conditions exist. Example screens of the controller's Ul are shown in Figures 2 12 and 16 and are described below.
  • the web reports server 36 provides functionality for allowing the operator to remotely monitor the operation of the transactional server 30, as measured and reported by the agent computers 40, using a standard web browser.
  • the reports server 36 could be configured to "push" the performance data, or reports generated therefrom, to a special client application for viewing.
  • the agent computers 40 preferably report their transaction execution results (performance data) to the reports server 36 in real time (preferably via the controller 34, which checks for predefined alert conditions), allowing operator to view the real time status of the transactional server.
  • the reports server 36 may optionally be implemented by a "monitoring service provider" entity that stores and provides secure access to server status data for many different transactional servers and business entities; this approach relieves the operator of the transactional server under test from having to administer the reports server 36.
  • each or some of the operators of the transactional servers under test could implement their own respective reports servers 36.
  • one important feature of the monitoring tool involves the ability of the user to monitor server performance according to operator selected attributes of the agent computers 40. For example, using the reports server, 36, the user could view a graph of the average response time as measured by all agent computers in San Francisco, or by all computers that use a particular ISP.
  • the attributes of each agent computer include the computer's location, organization, and ISP, and can be assigned or modified via the user interface of the controller 34 (see Figure 6).
  • Other types of attributes including user-defined attribute types, can additionally or alternatively be used.
  • An example of a report in which performance is displayed separately for each location and transaction is shown in Figure 15 and described below.
  • Another important feature involves the ability of the user to assign execution schedules to particular agent machines 40, including periodic schedules (e.g., once per hour on weekdays).
  • periodic schedules e.g., once per hour on weekdays.
  • the user can, for example, set up a monitoring session in which the transactional server 30 is proactivel ⁇ exercised and monitored on a continuous or near-continuous basis, and in which system administrators are notified immediately (such as by pager) as soon as an alert condition is detected.
  • distributed monitoring session or “distributed session” refers to a monitoring session in which multiple agent computers 40 are used to monitor a transactional server 30.
  • agent group refers to the group of agent computers 40 included within a distributed session.
  • agent refers either to the agent component 32 generally, or to a particular copy or instance of the agent component running on an agent computer, depending upon the context in which the term is used.
  • attribute refers to a particular characteristic or property of a host or agent computer, such as the location, organization, ISP, or configuration of the computer.
  • transactional server refers to a multi user system which responds to requests from users to perform one or more tasks or "transactions,” such as viewing account information, placing an order, performing a search, or viewing and sending electronic mail.
  • actions such as viewing account information, placing an order, performing a search, or viewing and sending electronic mail.
  • operator refers generally to a business entity that is responsible for the operation of the transactional server (typically the owner).
  • testcase refers generally to a computer representation of the transact ⁇ on(s) to be performed by a particular computer to monitor a transactional server, in the preferred embodiment, the testcases include conventional test scripts (either in textual or executable form) that are "played" by the agent computers 40, although the testcases could alternatively be in other forms. Testcases may optionally include verification points that are used to test server functionality.
  • web indicates the use of the World Wide Web standards, such as HTTP. III. Architecture and General Operation
  • the agent 32 is implemented using the commercially-available LoadRunner Virtual Machine
  • VUser component of Mercury Interactive Corporation, and is capable of executing testcases generated using Mercury Interactive's LoadRunner, WinRunner and Astra QuickTest products. Examples of methods that may be used to generate and play testcases are described in co pending U.S. applications 08/949,680 (filed October 14, 1997) and 09/337,446 (filed June 21, 1999). Other known programming methods for simulating user actions and monitoring server responses may be used to implement the agent 32; in addition, application-specific hardware could be used to perform some or ail of the agent's functions.
  • the agent 32 is installed on the agent computers 40 prior to initiation of monitoring sessions. Once installed, the agent can receive testcases and execution schedules from the controller 34 over the Internet or other TCP/IP based network via API calls. Alternatively, the agents 32 may be installed automatically by the controller 34 when a monitoring session is initiated. For example, the controller 34 could dispatch an agent 32 and a testcase (optionally as a single executable component) to each machine in the agent group, and the agents 32 could automatically delete themselves following testcase execution. Each agent 32 can preferably simulate the actions of multiple users.
  • the agent group is selected so as to encompass a representative cross section of client attributes.
  • one or more agent computers 40 may be selected within each geographic area and/or department from which significant user activity is expected to originate.
  • a monitoring service provider entity such as the entity that operates the reports server 36, may set up Internet hosts with various attributes (e.g., in various geographic locations, with a variety of different ISPs, etc.) and make such hosts available to its customers as agent computers 40.
  • host computers are preferably provided by the service provider with the agent 32 pre installed, and are configured to monitor multiple transactional servers (and thus service multiple operators) concurrently. This method is especially useful where the operator of the transactional server 30 would not otherwise have access to client computers with attributes of typical end users.
  • the controller 34 preferably includes or i ⁇ teroperates with a recorder 34A that provides functions for recording and editing transactions to be included within testcases.
  • a recorder 34A that provides functions for recording and editing transactions to be included within testcases.
  • any one or more of the above mentioned products of Mercury Interactive Corporation may be used as the recorder 34.
  • the user may optionally re-use testcases or testcase scripts that were created for pre-deplo ⁇ ment testing of the transactional server 36. Other existing tools and testcase generation methods could be used to generate the testcases.
  • the controller 34 also includes a scheduler component 34B that is used to set up monitoring sessions.
  • the scheduler 34B is preferably implemented using one or more "wizards" that step the user through the process of selecting agent computers, specifying the transactions to be performed by such computers, assigning execution schedules to the agent computers, and specifying criteria for generating alert events and notifications.
  • Example screen displays provided by the scheduler 34B are included in Figures 3 12 and are discussed below.
  • the controller 34 also includes an automation interface 34C that provides methods for controlling the operation of the agents 32, including dispatching testcases and execution schedules to the agents.
  • the automation interface is implemented using the LoadRunner 6.0 automation interface available from Mercury Interactive Corporation.
  • the controller 34 further includes an alerts engine 34D that monitors some or all of the performance data generated by the agents 32 in real-time to check for user defined alert conditions.
  • the alerts engine 34D can be configured to notify an operator of alert conditions by an appropriate communications method such as pager, cellular telephone, or email.
  • the alerts engine can be configured to page a system administrator whenever the average response time of the transactional server exceeds a certain threshold, or when the transactional server becomes inaccessible from any location or organization.
  • the alerts engine can be configured to page a system administrator whenever the average response time of the transactional server exceeds a certain threshold, or when the transactional server becomes inaccessible from any location or organization.
  • 34D can also generate notifications that are based on the content (e.g., expected text strings or values) returned by the transactional server.
  • the controller 34 stores various test control data in local storage 38.
  • the test control data typically includes testcase files (script files and related data files) for pre recorded transactions, and session files that specify the various monitoring sessions that have been created.
  • the reports server 36 provides online, web-based access to the testcase execution (performance) data reported in real-time by agents 32.
  • the performance data for the ongoing distributed sessions is stored within a central, "sessions" database 42, which is an ODBC compliant database in the preferred embodiment.
  • a central, "sessions" database 42 which is an ODBC compliant database in the preferred embodiment.
  • One possible schema of this database 40 is described below.
  • the components of the reports server 36 preferably include a web server 36A such as Microsoft Internet Information
  • IIS Internet Engineering Task Force
  • the database access layer 36C is implemented using a set of Active
  • .ASP files that use MDAC (Microsoft Data Access Components) to communicate with the sessions database 42.
  • the ASP pages include an administration page (not shown) that can be accessed by users with administrator privileges to perform such tasks as adding new end users to the database 42.
  • the report generation component 36D is implemented using Microsoft ActiveX Data Objects (ADO), which provides functions for generating dynamic web pages.
  • the dynamic web pages includes various pre defined graphs and charts (see Figures 13 16) that are used to build customized, web based reports.
  • the reports server 36 could also be configured to disseminate the reports by email, fax, a push protocol, or other communications method.
  • FIG. 2 illustrates the mam screen or console for a preferred embodiment of the controller 34, with an example monitoring session (also referred to as a "profile") open and displayed in the tree window.
  • the details of the monitoring session are graphically presented to the user as an expandable session tree 46 which shows the agent (host) computers, the testcase execution schedules assigned to each agent computer, and the transactions assigned to each agent computer.
  • the session tree also shows any alert conditions that have been defined.
  • the monitoring session uses a single agent computer, "idopc,” which has been assigned a single transaction "flights" and an execution schedule of "Every 5 minutes, Monday Friday, all day.”
  • the monitoring session includes a single alert under which an alert event will be triggered if the response time of the transaction "flights" exceeds 10 seconds.
  • the expandable tree can advantageously be used to edit a monitoring session through drag-and drop and other standard functions provided by the Windows operating system.
  • the controller's Ul also provides a browser window through which a user can view report pages from the reports server 36.
  • the controller's menu provides functions for performing various session related tasks, including launching the Setup and Alerts Wizards (described below), opening and editing an existing monitoring session, starting and stopping monitoring sessions, specifying the address of the reports server 36 to be used with a monitoring session, clearing the contents of the database 42, and specifying settings for sending alert notifications.
  • PROFILE/NEW which causes the controller 34 to launch a Setup Wizard ( Figures 3 9).
  • the user is initially prompted to specify a session name.
  • the session name provides a mechanism for later retrieving or viewing the reports for a particular monitoring session.
  • the user is then presented a "Select Transactions" screen for specifying the previously generated transactions to be included within the monitoring session.
  • the user can also use the NEW button to launch the recorder 34A and record a new transaction.
  • the transactions may optionally include verification points that specify expected server responses, such as particular values or text strings within web pages. Alternatively, the transactions may stress the transactional server without verifying the content of the server responses.
  • the user can later assign specific transactions, or sets of transactions, to specific agent computers 40, and can monitor the performance of the transactional server on a transaction by transaction basis.
  • the user can freely define what constitutes a "transaction" for monitoring purposes. For example, the user can start recording a user session, record any number of user interactions with the server (form submissions, page requests, etc.), stop recording, and then store the result as a transaction under a user specified name (e.g., "browse catalog").
  • a user specified name e.g., "browse catalog”
  • the user can optionally divide the transaction into multiple smaller transactions or make other modifications.
  • the transactions can also include accesses to multiple web sites.
  • the transactions are defined by the user with sufficient granularity to facilitate identification of performance bottlenecks. For example, the user may wish to create a separate transaction for each of the primary applications deployed on the transactional server 30 so that each such application can be monitored independently.
  • the transactions included within the session may optionally include special non destructive or "synthetic" transactions that do not change the state of the transactional server 30. If destructive transactions are used, the transactional server 30 may optionally be configured to handle such transaction in a special, do ⁇ -detructive manner. This may be accomplished, for example, by setting up dummy accounts for monitoring purposes. In addition, where appropriate, the transactional server 30 may be preprogrammed to roll back its databases, or to otherwise ignore the transaction, when a particular dummy account, credit card number, username, or other unique element is used.
  • the next step in the setup process involves selecting the computer or computers to be included in the agent group.
  • the user can view and select from a standard Windows NT ® tree view of the host computers that are available for use.
  • the tree view displays only those computers on which the agent 32 is installed.
  • the tree view also lists computers that do not have the agent 32 stored thereon, and provides an option for the user to remotely install the agent on such computers.
  • the computers that are available for use may optionally include computers that are made available by a monitoring service provider; in such implementations, the Setup Wizard 34 may be configured to automatically retrieve a list of such service provider computers and their respective attributes from a special Internet host. Techniques for generating and accessing lists of available servers are well known in the art, and are therefore not described herein.
  • the selected computers are added to the session tree 46 as respective nodes or icons.
  • the user When the user selects the EDIT button ( Figure 5) with a computer selected in the session tree 46, the user is presented with a "Computer Properties" screen as shown in Figure 6. From this screen, the user can assign various attributes (properties) to the computer or confirm previously-assigned attributes.
  • the attribute types are the location (e.g., city), organization (e.g., accounting department), and ISP of the agent computer 40.
  • Other pre-defined attributes types include, for example, a group name, the computer's operating system, the router to which the computer is connected, the computer's modem or other connection speed, the computer's default web browser (particularly if the agent uses or emulates the browser), and the hardware configuration of the computer.
  • controller 34 and the reports server 36 may provide the user an option to create one or more user-defined attribute types, and to use such attribute types in the same manner as the predefined attribute types. It should be understood, therefore, that the specific attributes and attributes types shown in the figures are merely illustrative, and are not intended to limit the invention.
  • the attributes that are assigned to the agent computers can be used to separately view the transactional server's performance as monitored by a particular attribute group (group of computers that share a particular attribute or set of attributes) For example, the user can view a graph of the response times measured by all agent computers with the location attribute "San Jose" or the ISP attribute "Sprint.” Example reports are shown in Figures 13 16 and are described below. The user can also generate attribute filtered reports to exclude performance data associated with specific attributes from consideration (as described below). The ability to view and monitor performance separately for each attribute group and to generate attribute filtered reports greatly facilitates the task of identifying attribute-specific performance problems.
  • an "Assign Transactions" screen ( Figure 7) appears. From this screen, the user can assign transactions (from the previously created transactions list) to specific computers in the agent group. The user can also specify, for each computer, the order in which that computer is to execute the assigned transactions. As transactions are assigned to agent computers 40, the transactions are added to the session tree 46 as children of their respective computers (as illustrated in Figures 7 and 8 for the computer "dolphin").
  • Period schedules may be used.
  • the periodic schedules may optionally include pseudo-random schedules.
  • the schedules are added to the session tree 46 as children of their respective agent computers. In other embodiments, the schedules may be assigned on a transaction-b ⁇ -transaction basis.
  • the execution schedules may be selected so as to provide continuous or near continuous monitoring of the transactional server 30. By staggering the execution schedules so that different agent computers 40 monitor the transactional server 30 at different times, the transactional server 30 can optionally be monitored continuously (24 hours per day) or nearly continuously without using any single agent computer 40 for an extended period of time. For example, if the agent computers 40 are distributed around the globe, the schedules can be assigned so that no agent computer 40 is used for testing during employee work hours within its respective region.
  • the Setup Wizard may optionally provide one or more functions (not illustrated) for assisting users in setting up continuous or near continuous monitoring sessions. For example, as the schedules are being assigned to agent computers, the wizard could automatically detect and display the "gaps" (periods of time during which the transactional server is not being monitored) in the cumulative execution schedule. The Setup Wizard could also provide an option to automatically generate an execution schedule which fills in these gaps. In addition, a function could be provided for ensuring that at least two agent computers 40 are scheduled to execute testcases at all times, so that the failure of a single agent computer will not cause the transactional server to go unmomtored
  • controller 34 dispatches the testcases and execution schedules to the respective agent computers 40, and sends various session configuration data (session name, transaction identifiers, attributes of agent computers, etc.) to the reports server 36 for storage in the sessions database 42.
  • the controller 40 also stores a representation of the monitoring session in local storage 38. The general flow of information to and from the controller computer 35 is described below with reference to the data flow drawings of Figures 17 and 18.
  • the user can select ALERT/ADD from the main menu to launch an Alerts Wizard ( Figures 10 12).
  • the Alerts Wizard allows the user to specify one or more performance parameters to monitor in real-time for purposes of generation alerts, including response time, availability, pass/fail status, and response data size.
  • the check box 70 the user can specify certain parameter statistics to monitor, such as the average of the parameter over a specified time frame.
  • the Alerts Wizard also provides screens for specifying notification criteria for the parameters to be monitored.
  • the user can request to be notified whenever the average response time exceeds a specified threshold, or exceeds the threshold with a specified frequency (e.g., 10 times per minute).
  • a specified frequency e.g. 10 times per minute.
  • the user can also request to be notified by pager or email of an alert condition.
  • the Alerts Wizard may also provide an option (not illustrated) to be notified when certain types of transactions fail, and/or when failures are detected within particular attribute groups. Using this option, a user can request to be notified whenever a problem is detected which falls within the user's respective area of responsibility. For example, a system administrator responsible for a particular business process may be notified when a transaction that corresponds to that business process fails; to avoid being notified of general failures, this notification may be made contingent upon other types of transactions completing successfully.
  • this feature includes: notifying an ISP administrator when a threshold number of agent computers using that ISP are unable to access to the transactional server (optionally contingent upon the transactional server being accessible from other ISPs); and notifying a system administrator responsible for a particular office when a threshold number of agent computers 40 within that office are unable to access to the transactional server (optionally contingent upon the transactional server being accessible from other offices).
  • the various functions of the controller 34 could be implemented in whole or in-part by the reports server 36.
  • the above described functions of the Alerts Wizard, and the associated functionality of the alerts engine 34D could additionally or alternatively be implemented by the reports server 36 such that users can remotely set up and modify alert conditions.
  • the task of checking for alarm conditions could also be performed by the agents 32.
  • the controller 34 is hosted by an ASP (application service provider) as a service that is accessed over the Internet using a conventional web browser.
  • ASP application service provider
  • each customer is given secure access to its respective repository of testcase and session files.
  • the service's user interface for setting up monitoring sessions may be generally the same as shown in Figures 2-12, with the dialog boxes replaced by corresponding web pages.
  • Test scripts may be recorded using a server-side recorder, and/or may be recorded by the customer using a downloadable recorder and then uploaded to the server.
  • the ASP which may also operate the reports server 36 and/or the agents computers 40, may charge customers for monitoring sessions based on one or more of the following criteria, as well as others: number of transaction types monitored, number of transaction execution events, quantity of hardware resources used, and time schedule and duration of monitoring sessions.
  • One important benefit of operating the controller 34 in this manner is that monitoring sessions can be initiated and modified from any computer that has Internet access, without the need for any special software.
  • Another benefit is that the customer is relieved of the burden have having to install and maintain the controller software.
  • the task of assigning execution schedules to the agent computers 40 may be performed by the ASP, rather than by the end user. This strategy is particularly useful where the agent computers 40 are shared by many different customers, as it allows the ASP to distribute the load across the agent computers so as to generally maximize the total number of distributed monitoring sessions that can exist concurrently.
  • a hybrid approach is also possible in which the customer controls the execution schedules of the customer's own agent computers 40 while the ASP controls the execution schedules of the shared agent computer's that are under the ASP's control.
  • the controller 34 may be hosted by a server on a private intranet, such as the intranet of the operator of the transactional server.
  • the controller preferably operates the same as if hosted by an ASP, but is private to the operator.
  • Figures 13-15 illustrate examples of the types of graphs or charts that may be provided by the reports server 36 to facilitate remote monitoring of the transactional server 30.
  • the examples shown in Figures 13-15 illustrate a monitoring session involving five transactions: Order Entry, Item in Stock Search, Browse Order Status, Update Account, and Purchase from Stock.
  • the transactions are being executed from agent computers 40 located in four geographic regions: New York, Japan, United Kingdom and San Francisco. More than one agent computer may be used in each such location.
  • the names and granularities of the geographic locations can be defined by the operator during the setup process.
  • the graphs indicate various aspects of the transactional server's performance as monitored over a particular time frame (the current day in this example).
  • the first graph 76 ( Figure 13) shows the minimum, average, and maximum transaction times for each of the five transactions.
  • the second graph 78 ( Figure 13) shows the average response time for each transaction and each one-hour interval, using a color coding scheme to distinguish between the transactions.
  • the third graph 80 ( Figure 14) shows the distribution of service levels for each of the five transactions, using a unique color for each level.
  • the fourth graph 82 shows, for each one-hour interval and each transaction, the percentage of transactions that failed.
  • the report pages preferably include various links and controls for allowing the user to generate customized and attribute filtered views of the performance data
  • a page appears which includes the graphs 84, 86 shown in Figure 15
  • Both graphs 84, 86 shows aspects of the server response time for the Browse Order Status transaction broken down by location, as may be desirable to identify location dependent problems
  • the horizontal line in these graphs 84, 86 represents a user defined alert threshold. From this page, the user can drill down an additional level (by selecting the location specific drill down links 90) to view location specific graphs for the Browse Order Status transaction.
  • the "Report Parameters" window 86 allows the user to modify the time frame and/or the breakdown method used to generate the various graphs and charts By modifying the breakdown method, the user can view the performance data separately for each transaction and for each attribute of the agent computers.
  • the performance data can be viewed by transaction (shown in Figures 13 and 14), by location (shown in Figure 15), by organization (not illustrated), and by ISP (not illustrated).
  • the performance data can be broken down according to other attribute types, including attribute types defined by the operator.
  • the "Filters” option 88 ( Figures 13 15) allows the user to filter the displayed information by transaction and by each of the attributes. Using this feature, the user can, for example, filter out from the reports the performance data corresponding to a particular transaction, location, organization, ISP, or combination thereof. In one embodiment (not shown), the user specifies the filter to be applied by completing a web form that includes a respective check box for each transaction and each attribute used in the monitoring session The application of a filter, if any, is indicated by the notations at the tops of the graphs (e.g., "Transactions: All; Locations: UK, NY, Organizations: accounting, marketing").
  • the Graph List option 90 allows the user to specify the set of default graphs that are to appear on the main status reports page.
  • the "Settings” option 92 allows the user to adjust and save other types of settings, such as an "auto refresh" rate (e.g., every five minutes) and a starting date/time to be used within the reports.
  • Figure 16 illustrates an example "Transaction Health Distribution" chart that may be generated by the reports server 36.
  • the chart is being viewed through the browser window of the controller's interface.
  • the chart is in the form of a 2 dimensional matrix.
  • the horizontal dimension represents the timeframe, which can be modified by the user over a range of hours to years
  • the columns represent hours of the current day (as displayed along the top of the chart), and the rows represent the transactions being monitored (as listed at the left).
  • the cells of the matrix are color coded to reflect the response time of the particular transaction during in the particular time frame.
  • Each hour and each transaction is a hyperlink that, when selected, causes the view to change.
  • the timeframe changes to just that hour with the matrix's horizontal dimension broken down into smaller (e.g., 5 or 10 minute) intervals.
  • the vertical dimension changes so that the chart shows only the selected transaction, broken down according to geographical location (or possibly another computer attribute).
  • attribute types are shown in the example reports, it should be understood that the illustrated features can be applied to other types of attributes, including user assigned attribute types.
  • the reports server 36 also preferably provides access to an Alerts chart (not shown) which contains information about the various alert events that have occurred.
  • this chart may include, for example, an alert name, a color-coded indication of the alert severity, the time of the alert event, the action taken (e.g.,
  • Figure 17 illustrates the "setup” or "programming" phase of a monitoring session. As depicted by the left-to- ⁇ ght arrows in Figure 17, once the user completes the setup process, the controller 34 dispatches the testcases
  • testcases and schedules to the respective agents 32.
  • agents 32 reside on remote agent computers 40
  • the testcases and schedules are communicated over the Internet using HTTP or another a TCP/IP based protocol via
  • the controller also sends session configuration data to the reports server 36 (preferably using HTTP) for storage in the sessions database 42.
  • the configuration data includes the session name, identifiers and properties (attributes) of the agent computers 40, and identifiers and names of the transactions.
  • the configuration data may also include a username or other identifier of the business entity to which the session corresponds.
  • Table 1 summarizes, for one example embodiment, the tables that are created in the sessions database 42 for each monitoring session and used to generate the reports. Any of a variety of alternative database schemas could be used.
  • the various metrics that are displayed in the reports (e.g , average response time over a particular window) are calculated using the data stored in the event meter table.
  • any alerts set up by the user are stored in local storage 38 along with session configuration data.
  • the alerts may additionally or alternatively be communicated to the reports server 36, in which case the reports server may handle the task of checking for and notifying users of alert conditions.
  • Figure 18 illustrates the flow of data for a representative, remote agent 32 as the agent executes a testcase.
  • the agent 32 interacts with (e.g., sends HTTP Post and Get messages to) the transactional server 30 while monitoring one or more predefined performance parameters such as response time.
  • the agent 32 also checks any verification points (e.g., expected values or text strings) defined within the testcase.
  • the agent 32 sends the resulting transaction execution data to the controller 34 using HTTP or another TCP/IP based protocol.
  • the transaction execution data preferably includes a transaction ID, the performance data (response time and pass/fail status) for the transaction, a transaction time/date stamp, and the host ID of the agent computer 40.
  • the agents could alternatively be designed to report their execution on a more or less frequent basis (e.g., once per server response, or once per testcase execution).
  • the controller 34 compares the performance data to any predefined alert conditions. If an alert condition is satisfied for which a notification message has been defined, the controller sends an alert notification message (represented by a dashed line in Figure 18) to the appropriate entity.
  • the recipient can log into the reports server 36 to obtain details of the alert event, such as the location or organization of the agent computer that reported associated performance data.
  • the alert events could also be stored locally to the controller computer and displayed within the session tree 46.
  • the controller 34 forwards the transaction execution data and any satisfied alert conditions to the web reports server 36 (preferably using the HTTP protocol) for insertion into the sessions database 42.
  • the controller preferably forwards the transaction execution data to the reports server 36 substantially in real time, on a transaction by transaction basis. This is accomplished in the preferred embodiment through an API of the automation interface 34C ( Figure 1 ).
  • the alert events are detected and reported to the reports server 36 in real-time by the alerts engine 34D. If multiple agents 32 are scheduled to execute testcases concurrently, the controller 34 processes the data streams from the multiple agents concurrently.
  • the main controller loop is thus in the form of:
  • the agents 32 could send the transaction execution data directly to the reports server 36, in which case the reports server 30 could optionally forward some or all of the execution data (e.g., alert conditions only) to the controller 34.
  • all agent computers 40 within a given location or organization could be configured to aggregate their performance data for transmission to or retrieval by the controller 34 or the reports server 36.
  • the task of checking for and notifying users of alert conditions could be performed by the agents 32 and/or by the reports server 30, rather than by the controller 34.
  • the agents 32 could be configured to "filter" the transaction execution data, so that only those transactions that meet certain predefined criteria are reported.
  • Figure 19 illustrates the process of remotely accessing the sessions database 42 using a standard web browser 100.
  • the user initially logs into his or her account using a username/password combination or other authentication method. Thereafter, the user views customized, real-time status reports (as described above) for the transaction server or servers corresponding to that account. As the reports pages are requested, the database 42 is accessed and the various performance metrics calculated using programming methods that are well known by those skilled in the art.
  • the first such feature involves having the agent computers 40 capture the screens returned by the transactional server 30 during transaction execution, and then forward these screen captures to the reports server 36 if the transaction is unsuccessful.
  • the reports server 36 displays, or presents an option to display, the captured sequence of screen displays for the failed transaction. For example, if the failed transaction involved an unexpected or missing message on a web page, the user could view the entire web page as well as the web pages (including any form data submitted by the agent) that preceded the unexpected response.
  • An important benefit of this feature is the ability for the user to view the sequence of events that led to the failed transaction.
  • Figure 20 illustrates the screen capture process as implemented within the agent component 32.
  • the agent captures the screen returned by the transactional server and compares this response against any associated verification points defined within the transaction.
  • the screen displays are preferably stored as bitmap images, but may alternatively be stored in another format such as HTML documents and associated objects.
  • the agent 32 determines whether the transaction completed successfully.
  • a transaction is preferably treated as unsuccessful if any verification point failed.
  • a transaction may also be treated as unsuccessful if, for example, a timeout event occurred.
  • the agent 32 sends the sequence of captured screen displays to the reports server 36 (block 120), which in turn stores the screen displays in the sessions database 42 for later viewing.
  • the screen displays could additionally or alternatively be sent by email to a human operator for viewing. If the transaction completes successfully, the screen displays are discarded without being forwarded to the reports server 36.
  • a second feature that may be incorporated into the agent 32 is an ability to measure and report segment delays incurred along a network path between an agent computer 40 and the transactional server 30.
  • the segment delays are preferably measured using the Network Monitor component of the commercially-available LoadRunner 6.0 product of Mercury Interactive Corporation.
  • some or all of the agents 32 are configured via the controller 34 to launch the Network Monitor (on their respective agent computers 40) when the path delay exceeds a preprogrammed threshold. These thresholds may optionally be specified by the user when setting up a monitoring session.
  • the Network Monitor measures the delay along each segment of the path between the relevant agent computer 40 and the transactional server 30 using well-known methods.
  • the agent 32 reports these measurements to the reports server 36, which allows the user to drill down and view the measurements.
  • the measured delays are preferably presented using the standard segment delay and path delay graphs provided within
  • the segment delay data may be used, for example, to detect router problems or bottlenecks in network architectures.
  • a third feature involves the ability of the agents 32 to detect and report "broken links" (links to inaccessible files or other objects) within web sites.
  • the user can remotely program one or more of the agent computers 40 to crawl the web site periodically (e.g., once per day) to check for broken links, and to report any broken links that are found.
  • a list of the broken links may automatically be posted to the reports server 36 for viewing and/or be sent to the user by email.
  • Each broken link may be reported to the user in the form of a URL pair that indicates the respective locations of the missing object and the page containing the broken link.
  • Techniques for crawling web sites and checking for broken links are well known in the art, and are described, for example, in U.S. Patent No. 5,958,008 of Mercury Interactive Corporation
  • the reports server 40 preferably allows the user to separately view the attributes of the agent computers that experienced the problem.

Abstract

A monitoring system allows users to monitor the post-deployment performance of a web-based or other transactional server (30). The system includes an agent component ('agent') (32) which can be installed on agent computers (40) that have access to the transactional server (30), including computers of actual users of the transactional server (30). The agent (32) simulates the actions of actual users of the transactional server (30) while monitoring the server's performance. The specific transactions to be performed by the agent computers (40) are specified by testcases that are dispatched to the agent computers (40) using a controller (34). As each agent computer (40) executes a testcase, it reports the execution results (performance data) in real-time to a web-based reports server (36) which stores the results in a centralized database (42). The performance data may include, for example, server response times, screen display sequences for failed transactions, measured segment delays along network paths, and identifiers of 'broken' web site links. Authorized personnel can access the reports server (36) using a standard web browser to view the collected performance data via a series of customizable reports. Using the controller (34), the user can also assign testcase execution schedules to the agent computers (40), including periodic schedules that provide for continuous or near-continuous monitoring of the transactional server (30). In addition, the user can specify alert conditions which cause personnel to be immediately notified (e.g., by pager) of problems. The controller (34) and the reports server (36) also provide functions for allowing the user to monitor the operation of the transactional server (30) according to the attributes of the agent computers (40), such as the locations, organizations, and ISPs of such computers.

Description

POST-DEPLOYMENT MONITORING OF SERVER PERFORMANCE Field of the Invention The present invention relates to software tools for testing and monitoring the operation of web-based and other transactional servers.
Background of the Invention A variety of commercially-available software tools exist for assisting companies in testing the performance and functionality of their web-based transactional servers and associated applications prior to deployment. Examples of such tools include the LoadRunner®, WinRunner® and Astra QuickTest® products of Mercury Interactive Corporation, the assignee of the present application.
Using these products, a user can record or otherwise create a test script which specifies a sequence of user interactions with the transactional server. The user may also optionally specify certain expected responses from the transactional server, which may be added to the test script as verification points. For example, the user may record a session with a web-based travel reservation system during which the user searches for a particular flight, and may then define one or more verification points to check for an expected flight number, departure time or ticket price.
Test scripts generated through this process are "played" or "executed" to simulate the actions of users - typically prior to deployment of the component being tested. During this process, the testing tool monitors the performance of the transactional server, including determining the pass/fail status of any verification points. Multiple test scripts may be replayed concurrently to simulate the load of a large number of users. Using an automation interface of the LoadRunner product, it is possible to dispatch test scripts to remote computers for execution.
The results of the test are typically communicated to the user through a series of reports that are accessible through the user interface of the testing tool. The reports may contain, for example, graphs or charts of the observed response times for various types of transactions. Performance problems discovered through the testing process may be corrected by programmers or system administrators. A variety of tools and services also exist that allow web site operators to monitor the post-deployment performance of their web sites. For example, Keynote Systems Inc. of San Mateo California provides a service which uses automated agents to access a web site at regular intervals throughout the day. The agents computers, which are provided by Keynote Systems in selected major cities, measure the time required to perform various web site functions, and report the results to a server provided by Keynote Systems. The owner or operator of the web site can access this server using a web browser to view the collected performance data on a city-bγ-citγ or other basis. Other types of existing monitoring tools include log analysis tools that process access logs generated by web servers, and packet sniffing tools that monitor traffic to and from the web server. Summary of the Invention A significant problem with existing monitoring tools and services is that they often fail to detect problems that are dependent upon the attributes of typical end users, such as the user's location, PC configuration, ISP (Internet Service Provider), or Internet router. For example, with some web site monitoring services, the web site operator can monitor the web site only from the agent computers and locations made available by the service provider; as a result, the service may not detect a performance problem seen by the most frequent users of the system (e.g., members of a customer service department who access the web site through a particular ISP, or who use a particular PC configuration).
Even when such attribute specific problems are detected, existing tools and services often fail to identify the specific attributes that give rise to the problem. For example, a monitoring service may indicate that web site users in a particular city are experiencing long delays, but may fail to reveal that the problem is experienced only by users that access the site through a particular router. Without such additional information, system administrators may not be able to isolate and correct such problems.
Another significant problem with existing tools and services is that they do not provide an adequate mechanism for monitoring the current status of the transactional server, and for promptly notifying system administrators when a problem occurs. For example, existing tools and services typically do not report a problem until many minutes or hours after the problem has occurred. As a result, many end users may experience the problem before a system administrator becomes aware of the problem.
The present invention addresses these and other problems by providing a software system and method for monitoring the post-deployment operation of a web site system or other transactional server. In a preferred embodiment, the system includes an agent component ("agent") which simulates the actions of actual users of the transactional server while monitoring and reporting the server's performance. In accordance with one aspect of the invention, the agent is adapted to be installed on selected computers ("agent computers") to be used for monitoring, including computers of actual end users. For example, the agent could be installed on selected end-user computers within the various offices or organizations from which the transactional server is commonly accessed. Once the agent component has been installed, the agent computers can be remotely programmed (typically by the operator of the transactional server) using a controller component ("controller"). The ability to flexibly select the computers to be used for monitoring purposes, and to use actual end-user computers for monitoring, greatly facilitates the task of detecting problems associated with the attributes of typical end users. In accordance with another aspect of the invention, the controller provides a user interface and various functions for a user to remotely select the agent computer(s) to include in a monitoring session, assign attributes to such computers (such as the location, organization, ISP and/or configuration of each computer), and assign transactions and execution schedules to such computers The execution schedules may be periodic or repetitive schedules, (e.g., every hour, Monday through Friday), so that the transactional server is monitored on a continuous or near-continuous basis. The controller preferably represents the monitoring session on the display screen as an expandable tree in which the transactions and execution schedules are represented as children of the corresponding computers. Once a monitoring session has been defined, the controller dispatches the transactions and execution schedules to the respective agent computers over the Internet or other network. The controller also preferably includes functions for the user to record and edit transactions, and to define alert conditions for generating real-time alert notifications. The controller may optionally be implemented as a hosted application on an Internet or intranet site, in which case users may be able to remotely set up monitoring sessions using an ordinary web browser.
During the monitoring session, each agent computer executes its assigned transactions according to its assigned execution schedule, and generates performance data that indicates one or more characteristics of the transactional server's performance. The performance data may include, for example, the server response time and pass/fail status of each transaction execution event. The pass/fail status values may be based on verification points
(expected server responses) that are defined within the transactions. The agent computers preferably report the performance data associated with a transaction immediately after transaction execution, so that the performance data is available substantially in real time for viewing and generation of alert notifications. In the preferred embodiment, the performance data generated by the various agent computers is aggregated in a centralized database which is remotely accessible through a web-based reports server. The reports server provides various user-configurable charts and graphs that allow the operator of the transactional server to view the performance data associated with each transaction.
In accordance with another aspect of the invention, the reports server generates reports which indicate the performance of the transactional server separately for the various operator-specified attributes. Using this feature, the user can, for example, view and compare the performance of the transactional server as seen from different operator-specified locations (e.g., New York, San Francisco, and U.K.), organizations (e.g., accounting, marketing, and customer service departments), ISPs (e.g., Spring, AOL and Earthlink), or other attribute type. The user may also have the option to filter out data associated with particular attributes and/or transactions (e.g., exclude data associated with AOL customers), and to define new attribute types (e.g., modem speed or operating system) for partitioning the performance data. The ability to monitor the performance data according to the operator specified attributes greatly facilitates the task of isolating and correcting attribute-dependant performance problems.
In accordance with another aspect of the invention, the performance data is monitored substantially in real time (preferably by the controller) to check for any user defined alert conditions. When such an alert condition is detected, a notification message may be sent by email, pager, or other communications method to an appropπate person. The alert conditions may optionally be specific to a particular location, organization, ISP, or other attribute.
For example, a system administrator responsible for an Atlanta branch office may request to be notified when a particular problem (e.g., average response time exceeds a particular threshold) is detected by computers in that office In the preferred embodiment, upon receiving an alert notification, the administrator can use a standard web browser to access the reports server and view the details of the event or events that triggered the notification. In accordance with another aspect of the invention, the agent computers may be programmed to capture sequences of screen displays during transaction execution, and to transmit these screen displays to the reports server for viewing when a transaction fails. This feature allows the user to view the sequence of events, as "seen" by an agent, that led to the error condition In accordance with another feature of the invention, an agent computer may be programmed to launch a network monitor component when the path delay between the agent computer and the transactional server exceeds a preprogrammed threshold. Upon being launched, the network monitor component determines the delays currently being experienced along each segment of the network path The measured segment delays are reported to personnel (preferably through the reports server), and may be used to detect various types of network problems. In accordance with another aspect of the invention, one or more of the agent computers may be remotely programmed to scan or crawl the monitored web site periodically to check for broken links (links to inaccessible objects). When broken links are detected, they may be reported by email, through the reports server, or by other means.
Brief Description of the Drawings A distributed monitoring tool and associated methods that embody the various inventive features will now be described with reference to the following drawings:
Figure 1 illustrates the general architecture of the monitoring tool, and illustrates how the monitoring tool may be used to monitor the performance of a web based transactional server.
Figure 2 illustrates a main user interface screen of the controller depicted in Figure 1. Figures 3 9 illustrate the controller's Setup Wizard screens that are used to set up monitoring sessions,
Figures 10 12 illustrate screens of the controller's Alerts Wizard;
Figure 13 16 illustrate example status report web pages provided by the web reports server in Figure 1, with Figure 14 illustrating a representative "drill down" page returned when the user selects the drill down link in Figure 13 for the "browse order status" transaction. Figures 17 19 are flow diagrams that illustrate the flow of information between components during the setup and execution of a monitoring session.
Figure 20 illustrates a process for capturing screen displays on failed transactions. Detailed Description of the Preferred Embodiment The following description sets forth numerous implementation-specific details of a distributed monitoring tool and associated methods. These details are provided in order to illustrate a preferred embodiment of the invention, and not to limit the scope of the invention. The scope of the invention is defined only by the appended claims
Throughout this description, it will be assumed that the transactional server being monitored is a web based system that is accessible via the Internet. It will be recogmzed, however, that the inventive methods can also be used to monitor other types of transactional servers, including those that use proprietary protocols or are accessible only to internal users of a particular organization. For example, the underlying methodology can also be used to monitor internal intranets, two-tier client/server systems, SAP R/3 systems, and other types of distributed systems. I. Overview
Figure 1 illustrates the general components of the distributed monitoring tool, and illustrates how these components may be deployed within a network to test and monitor a web based transactional server 30. Dashed lines in Figure 1 indicate typical machine boundaries, with open boxes indicating one or more machines. As depicted by Figure 1, the transactional server 30 typically includes a web server component 30A and one or more applications 30B The applications may, for example, provide functionality for implementing one or more business processes, such as setting up a user account or placing an order. The applications 30B typically provide user access to one or more back end databases (not shown). The transactional server may include multiple machines, including machines that are geographically remote from one another.
As further depicted by Figure 1, the monitoring tool consists of three primary software components: an agent 32, a controller 34 and a web based reports server 36. Each component 32, 34, 36 includes one or more executable files or modules stored within a computer-readable medium. The agent 32 includes the basic functionality for simulating the actions of users of the transactional server
30 while monitoring and reporting server performance. As illustrated in Figure 1, the agent 32 is preferably installed on multiple Internet-connected host computers 40 (PCs, workstations, etc.) so that the end user experience can be captured from multiple locations. These host computers 40 may advantageously include computers that are owned or controlled by the operator of the transactional server 30. For example, the operator of the transactional server can install the agent component on selected computers within each of the departments or organizations from which the transactional server is frequently accessed, including computers of actual end users.
For convenience, the computers 40 that host the agent 32 will be referred to as "agent computers," and a computer 35 that hosts the controller 34 will be referred to as a "controller computer." It should be understood, however, that a single computer could host two or more of the tool's components 32, 34, and 36, and that the functionality of the monitoring tool could be divided differently between components. In addition, the web reports server 36 and the transactional server 30 could be accessed through a common web site.
The controller 34 provides a user interface (Ul) through which the operator of the transactional server can set up and initiate monitoring sessions, including distributed monitoring sessions in which the transactional server is accessed and monitored from multiple user locations. Through this Ul, the user can, among other things, select the agent computers 40 to be included within a monitoring session, and assign transactions and execution schedules to such computers. The controller 34 also provides functions for specifying alert conditions, and for notifying personnel when such conditions exist. Example screens of the controller's Ul are shown in Figures 2 12 and 16 and are described below.
The web reports server 36 provides functionality for allowing the operator to remotely monitor the operation of the transactional server 30, as measured and reported by the agent computers 40, using a standard web browser. In other embodiments, the reports server 36 could be configured to "push" the performance data, or reports generated therefrom, to a special client application for viewing. As described below, the agent computers 40 preferably report their transaction execution results (performance data) to the reports server 36 in real time (preferably via the controller 34, which checks for predefined alert conditions), allowing operator to view the real time status of the transactional server. The reports server 36 may optionally be implemented by a "monitoring service provider" entity that stores and provides secure access to server status data for many different transactional servers and business entities; this approach relieves the operator of the transactional server under test from having to administer the reports server 36. Alternatively, each or some of the operators of the transactional servers under test could implement their own respective reports servers 36. As described below, one important feature of the monitoring tool involves the ability of the user to monitor server performance according to operator selected attributes of the agent computers 40. For example, using the reports server, 36, the user could view a graph of the average response time as measured by all agent computers in San Francisco, or by all computers that use a particular ISP. In one embodiment, the attributes of each agent computer include the computer's location, organization, and ISP, and can be assigned or modified via the user interface of the controller 34 (see Figure 6). Other types of attributes, including user-defined attribute types, can additionally or alternatively be used. An example of a report in which performance is displayed separately for each location and transaction is shown in Figure 15 and described below.
Another important feature involves the ability of the user to assign execution schedules to particular agent machines 40, including periodic schedules (e.g., once per hour on weekdays). Using this feature, the user can, for example, set up a monitoring session in which the transactional server 30 is proactivelγ exercised and monitored on a continuous or near-continuous basis, and in which system administrators are notified immediately (such as by pager) as soon as an alert condition is detected. II. Terminology
To facilitate an understanding of the invention, the following terminology will be used throughout the remaining description:
The term "distributed monitoring session" or "distributed session" refers to a monitoring session in which multiple agent computers 40 are used to monitor a transactional server 30.
The term "agent group" refers to the group of agent computers 40 included within a distributed session.
The term "agent" refers either to the agent component 32 generally, or to a particular copy or instance of the agent component running on an agent computer, depending upon the context in which the term is used.
The term "attribute" refers to a particular characteristic or property of a host or agent computer, such as the location, organization, ISP, or configuration of the computer.
The term "transactional server" refers to a multi user system which responds to requests from users to perform one or more tasks or "transactions," such as viewing account information, placing an order, performing a search, or viewing and sending electronic mail. The term "operator" refers generally to a business entity that is responsible for the operation of the transactional server (typically the owner).
The term "testcase" refers generally to a computer representation of the transactιon(s) to be performed by a particular computer to monitor a transactional server, in the preferred embodiment, the testcases include conventional test scripts (either in textual or executable form) that are "played" by the agent computers 40, although the testcases could alternatively be in other forms. Testcases may optionally include verification points that are used to test server functionality.
The term "web" indicates the use of the World Wide Web standards, such as HTTP. III. Architecture and General Operation In a preferred embodiment, the agent 32 is implemented using the commercially-available LoadRunner Virtual
User (VUser) component of Mercury Interactive Corporation, and is capable of executing testcases generated using Mercury Interactive's LoadRunner, WinRunner and Astra QuickTest products. Examples of methods that may be used to generate and play testcases are described in co pending U.S. applications 08/949,680 (filed October 14, 1997) and 09/337,446 (filed June 21, 1999). Other known programming methods for simulating user actions and monitoring server responses may be used to implement the agent 32; in addition, application-specific hardware could be used to perform some or ail of the agent's functions.
In the preferred embodiment, the agent 32 is installed on the agent computers 40 prior to initiation of monitoring sessions. Once installed, the agent can receive testcases and execution schedules from the controller 34 over the Internet or other TCP/IP based network via API calls. Alternatively, the agents 32 may be installed automatically by the controller 34 when a monitoring session is initiated. For example, the controller 34 could dispatch an agent 32 and a testcase (optionally as a single executable component) to each machine in the agent group, and the agents 32 could automatically delete themselves following testcase execution. Each agent 32 can preferably simulate the actions of multiple users.
Preferably, the agent group is selected so as to encompass a representative cross section of client attributes. For example, one or more agent computers 40 may be selected within each geographic area and/or department from which significant user activity is expected to originate. in addition, a monitoring service provider entity, such as the entity that operates the reports server 36, may set up Internet hosts with various attributes (e.g., in various geographic locations, with a variety of different ISPs, etc.) and make such hosts available to its customers as agent computers 40. Such host computers are preferably provided by the service provider with the agent 32 pre installed, and are configured to monitor multiple transactional servers (and thus service multiple operators) concurrently. This method is especially useful where the operator of the transactional server 30 would not otherwise have access to client computers with attributes of typical end users. For example, an operator of an electronic commerce Web site may not have access to host computers within the various countries or regions from which purchases are made. The method also relieves the operator of the burden of setting up and administering the agent computers 40. As illustrated in Figure 1 , the controller 34 preferably includes or iπteroperates with a recorder 34A that provides functions for recording and editing transactions to be included within testcases. In a preferred embodiment, any one or more of the above mentioned products of Mercury Interactive Corporation may be used as the recorder 34. Rather than recording new testcases, the user may optionally re-use testcases or testcase scripts that were created for pre-deploγment testing of the transactional server 36. Other existing tools and testcase generation methods could be used to generate the testcases.
The controller 34 also includes a scheduler component 34B that is used to set up monitoring sessions. The scheduler 34B is preferably implemented using one or more "wizards" that step the user through the process of selecting agent computers, specifying the transactions to be performed by such computers, assigning execution schedules to the agent computers, and specifying criteria for generating alert events and notifications. Example screen displays provided by the scheduler 34B are included in Figures 3 12 and are discussed below.
The controller 34 also includes an automation interface 34C that provides methods for controlling the operation of the agents 32, including dispatching testcases and execution schedules to the agents. In a preferred embodiment, the automation interface is implemented using the LoadRunner 6.0 automation interface available from Mercury Interactive Corporation. The controller 34 further includes an alerts engine 34D that monitors some or all of the performance data generated by the agents 32 in real-time to check for user defined alert conditions. Using the scheduler 34B, the alerts engine 34D can be configured to notify an operator of alert conditions by an appropriate communications method such as pager, cellular telephone, or email. For example, the alerts engine can be configured to page a system administrator whenever the average response time of the transactional server exceeds a certain threshold, or when the transactional server becomes inaccessible from any location or organization. The alerts engine
34D can also generate notifications that are based on the content (e.g., expected text strings or values) returned by the transactional server.
As depicted in Figure 1, the controller 34 stores various test control data in local storage 38. The test control data typically includes testcase files (script files and related data files) for pre recorded transactions, and session files that specify the various monitoring sessions that have been created.
As indicated above, the reports server 36 provides online, web-based access to the testcase execution (performance) data reported in real-time by agents 32. As depicted in Figure 1, the performance data for the ongoing distributed sessions is stored within a central, "sessions" database 42, which is an ODBC compliant database in the preferred embodiment. One possible schema of this database 40 is described below. As depicted by Figure 1, the components of the reports server 36 preferably include a web server 36A such as Microsoft Internet Information
Server (IIS), an access control layer 36B which restricts access to the sessions database 42, a database access layer
36C, and a report generation component 36D. The database access layer 36C is implemented using a set of Active
Server Pages (.ASP files) that use MDAC (Microsoft Data Access Components) to communicate with the sessions database 42. The ASP pages include an administration page (not shown) that can be accessed by users with administrator privileges to perform such tasks as adding new end users to the database 42. The report generation component 36D is implemented using Microsoft ActiveX Data Objects (ADO), which provides functions for generating dynamic web pages. The dynamic web pages includes various pre defined graphs and charts (see Figures 13 16) that are used to build customized, web based reports. The reports server 36 could also be configured to disseminate the reports by email, fax, a push protocol, or other communications method. IV. Controller Ul and Session Setup
Figure 2 illustrates the mam screen or console for a preferred embodiment of the controller 34, with an example monitoring session (also referred to as a "profile") open and displayed in the tree window. The details of the monitoring session are graphically presented to the user as an expandable session tree 46 which shows the agent (host) computers, the testcase execution schedules assigned to each agent computer, and the transactions assigned to each agent computer. The session tree also shows any alert conditions that have been defined. In the simple example shown in Figure 2, the monitoring session uses a single agent computer, "idopc," which has been assigned a single transaction "flights" and an execution schedule of "Every 5 minutes, Monday Friday, all day." The monitoring session includes a single alert under which an alert event will be triggered if the response time of the transaction "flights" exceeds 10 seconds. The expandable tree can advantageously be used to edit a monitoring session through drag-and drop and other standard functions provided by the Windows operating system. As illustrated in Figure 16, the controller's Ul also provides a browser window through which a user can view report pages from the reports server 36.
The controller's menu, the top level of which is shown in Figure 2, provides functions for performing various session related tasks, including launching the Setup and Alerts Wizards (described below), opening and editing an existing monitoring session, starting and stopping monitoring sessions, specifying the address of the reports server 36 to be used with a monitoring session, clearing the contents of the database 42, and specifying settings for sending alert notifications.
To create a new monitoring session, the user selects PROFILE/NEW, which causes the controller 34 to launch a Setup Wizard (Figures 3 9). As illustrated by Figure 3, the user is initially prompted to specify a session name. The session name provides a mechanism for later retrieving or viewing the reports for a particular monitoring session. As illustrated in Figure 4, the user is then presented a "Select Transactions" screen for specifying the previously generated transactions to be included within the monitoring session. The user can also use the NEW button to launch the recorder 34A and record a new transaction. The transactions may optionally include verification points that specify expected server responses, such as particular values or text strings within web pages. Alternatively, the transactions may stress the transactional server without verifying the content of the server responses. As described below, the user can later assign specific transactions, or sets of transactions, to specific agent computers 40, and can monitor the performance of the transactional server on a transaction by transaction basis.
In the preferred embodiment, the user can freely define what constitutes a "transaction" for monitoring purposes. For example, the user can start recording a user session, record any number of user interactions with the server (form submissions, page requests, etc.), stop recording, and then store the result as a transaction under a user specified name (e.g., "browse catalog"). In addition, during subsequent editing of the transaction, the user can optionally divide the transaction into multiple smaller transactions or make other modifications. The transactions can also include accesses to multiple web sites. Preferably, the transactions are defined by the user with sufficient granularity to facilitate identification of performance bottlenecks. For example, the user may wish to create a separate transaction for each of the primary applications deployed on the transactional server 30 so that each such application can be monitored independently.
The transactions included within the session may optionally include special non destructive or "synthetic" transactions that do not change the state of the transactional server 30. If destructive transactions are used, the transactional server 30 may optionally be configured to handle such transaction in a special, doπ-detructive manner. This may be accomplished, for example, by setting up dummy accounts for monitoring purposes. In addition, where appropriate, the transactional server 30 may be preprogrammed to roll back its databases, or to otherwise ignore the transaction, when a particular dummy account, credit card number, username, or other unique element is used.
As illustrated by the "Select Computers" screen in Figure 5, the next step in the setup process involves selecting the computer or computers to be included in the agent group. By selecting the ADD button from this screen, the user can view and select from a standard Windows NT® tree view of the host computers that are available for use. In one embodiment, the tree view displays only those computers on which the agent 32 is installed. In another embodiment, the tree view also lists computers that do not have the agent 32 stored thereon, and provides an option for the user to remotely install the agent on such computers. As indicated above, the computers that are available for use may optionally include computers that are made available by a monitoring service provider; in such implementations, the Setup Wizard 34 may be configured to automatically retrieve a list of such service provider computers and their respective attributes from a special Internet host. Techniques for generating and accessing lists of available servers are well known in the art, and are therefore not described herein. The selected computers are added to the session tree 46 as respective nodes or icons.
When the user selects the EDIT button (Figure 5) with a computer selected in the session tree 46, the user is presented with a "Computer Properties" screen as shown in Figure 6. From this screen, the user can assign various attributes (properties) to the computer or confirm previously-assigned attributes. In the illustrated example, the attribute types are the location (e.g., city), organization (e.g., accounting department), and ISP of the agent computer 40. Other pre-defined attributes types that may be provided include, for example, a group name, the computer's operating system, the router to which the computer is connected, the computer's modem or other connection speed, the computer's default web browser (particularly if the agent uses or emulates the browser), and the hardware configuration of the computer. In addition, the controller 34 and the reports server 36 may provide the user an option to create one or more user-defined attribute types, and to use such attribute types in the same manner as the predefined attribute types. It should be understood, therefore, that the specific attributes and attributes types shown in the figures are merely illustrative, and are not intended to limit the invention.
The attributes that are assigned to the agent computers can be used to separately view the transactional server's performance as monitored by a particular attribute group (group of computers that share a particular attribute or set of attributes) For example, the user can view a graph of the response times measured by all agent computers with the location attribute "San Jose" or the ISP attribute "Sprint." Example reports are shown in Figures 13 16 and are described below. The user can also generate attribute filtered reports to exclude performance data associated with specific attributes from consideration (as described below). The ability to view and monitor performance separately for each attribute group and to generate attribute filtered reports greatly facilitates the task of identifying attribute-specific performance problems.
When the user selects the NEXT button from the Select Computers screen, an "Assign Transactions" screen (Figure 7) appears. From this screen, the user can assign transactions (from the previously created transactions list) to specific computers in the agent group. The user can also specify, for each computer, the order in which that computer is to execute the assigned transactions. As transactions are assigned to agent computers 40, the transactions are added to the session tree 46 as children of their respective computers (as illustrated in Figures 7 and 8 for the computer "dolphin").
When the user selects the NEXT button from the Assign Transactions screen, an "Assign Schedules" screen appears (Figure 8) that allows the user to assign a testcase execution schedule to each computer. When the user selects the SCHEDULE button with a computer selected in the session tree 46, a "Schedule Properties" box appears
(Figure 9). From the Schedule Properties box, the user can select a predefined execution schedule (e.g., "weekdays") to assign to the computer and/or define a new schedule. As illustrated in Figure 9, periodic schedules may be used. The periodic schedules may optionally include pseudo-random schedules. As shown in Figure 8, the schedules are added to the session tree 46 as children of their respective agent computers. In other embodiments, the schedules may be assigned on a transaction-bγ-transaction basis.
The execution schedules may be selected so as to provide continuous or near continuous monitoring of the transactional server 30. By staggering the execution schedules so that different agent computers 40 monitor the transactional server 30 at different times, the transactional server 30 can optionally be monitored continuously (24 hours per day) or nearly continuously without using any single agent computer 40 for an extended period of time. For example, if the agent computers 40 are distributed around the globe, the schedules can be assigned so that no agent computer 40 is used for testing during employee work hours within its respective region.
The Setup Wizard may optionally provide one or more functions (not illustrated) for assisting users in setting up continuous or near continuous monitoring sessions. For example, as the schedules are being assigned to agent computers, the wizard could automatically detect and display the "gaps" (periods of time during which the transactional server is not being monitored) in the cumulative execution schedule. The Setup Wizard could also provide an option to automatically generate an execution schedule which fills in these gaps. In addition, a function could be provided for ensuring that at least two agent computers 40 are scheduled to execute testcases at all times, so that the failure of a single agent computer will not cause the transactional server to go unmomtored
When the user selects the FINISH button (Figure 8) from the Assign Schedules box, the Setup Wizard closes and the user is presented with a view of the complete session tree 46 At this point, controller 34 dispatches the testcases and execution schedules to the respective agent computers 40, and sends various session configuration data (session name, transaction identifiers, attributes of agent computers, etc.) to the reports server 36 for storage in the sessions database 42. The controller 40 also stores a representation of the monitoring session in local storage 38. The general flow of information to and from the controller computer 35 is described below with reference to the data flow drawings of Figures 17 and 18. Once the setup process is completed, the monitoring session continues indefinitely until halted or terminated by the user.
With the session open within the controller's console (Figure 2), the user can select ALERT/ADD from the main menu to launch an Alerts Wizard (Figures 10 12). As illustrated by Figure 10, the Alerts Wizard allows the user to specify one or more performance parameters to monitor in real-time for purposes of generation alerts, including response time, availability, pass/fail status, and response data size. By selecting the check box 70, the user can specify certain parameter statistics to monitor, such as the average of the parameter over a specified time frame.
As illustrated by Figure 11 and 12, the Alerts Wizard also provides screens for specifying notification criteria for the parameters to be monitored. In the example shown in Figure 1 1, the user can request to be notified whenever the average response time exceeds a specified threshold, or exceeds the threshold with a specified frequency (e.g., 10 times per minute). As shown in Figure 12, the user can also request to be notified by pager or email of an alert condition.
The Alerts Wizard may also provide an option (not illustrated) to be notified when certain types of transactions fail, and/or when failures are detected within particular attribute groups. Using this option, a user can request to be notified whenever a problem is detected which falls within the user's respective area of responsibility. For example, a system administrator responsible for a particular business process may be notified when a transaction that corresponds to that business process fails; to avoid being notified of general failures, this notification may be made contingent upon other types of transactions completing successfully. Other example uses of this feature include: notifying an ISP administrator when a threshold number of agent computers using that ISP are unable to access to the transactional server (optionally contingent upon the transactional server being accessible from other ISPs); and notifying a system administrator responsible for a particular office when a threshold number of agent computers 40 within that office are unable to access to the transactional server (optionally contingent upon the transactional server being accessible from other offices).
In other embodiments of the invention, the various functions of the controller 34 could be implemented in whole or in-part by the reports server 36. For example, the above described functions of the Alerts Wizard, and the associated functionality of the alerts engine 34D, could additionally or alternatively be implemented by the reports server 36 such that users can remotely set up and modify alert conditions. The task of checking for alarm conditions could also be performed by the agents 32.
In one embodiment, the controller 34 is hosted by an ASP (application service provider) as a service that is accessed over the Internet using a conventional web browser. Through the ASP's servers, each customer is given secure access to its respective repository of testcase and session files. The service's user interface for setting up monitoring sessions may be generally the same as shown in Figures 2-12, with the dialog boxes replaced by corresponding web pages. Test scripts (transactions) may be recorded using a server-side recorder, and/or may be recorded by the customer using a downloadable recorder and then uploaded to the server. The ASP, which may also operate the reports server 36 and/or the agents computers 40, may charge customers for monitoring sessions based on one or more of the following criteria, as well as others: number of transaction types monitored, number of transaction execution events, quantity of hardware resources used, and time schedule and duration of monitoring sessions. One important benefit of operating the controller 34 in this manner is that monitoring sessions can be initiated and modified from any computer that has Internet access, without the need for any special software. Another benefit is that the customer is relieved of the burden have having to install and maintain the controller software.
In embodiments in which the controller 34 is hosted as a service, the task of assigning execution schedules to the agent computers 40 may be performed by the ASP, rather than by the end user. This strategy is particularly useful where the agent computers 40 are shared by many different customers, as it allows the ASP to distribute the load across the agent computers so as to generally maximize the total number of distributed monitoring sessions that can exist concurrently. A hybrid approach is also possible in which the customer controls the execution schedules of the customer's own agent computers 40 while the ASP controls the execution schedules of the shared agent computer's that are under the ASP's control.
In yet other embodiments, the controller 34 may be hosted by a server on a private intranet, such as the intranet of the operator of the transactional server. In such configurations, the controller preferably operates the same as if hosted by an ASP, but is private to the operator.
V. Performance Reports
Figures 13-15 illustrate examples of the types of graphs or charts that may be provided by the reports server 36 to facilitate remote monitoring of the transactional server 30. The examples shown in Figures 13-15 illustrate a monitoring session involving five transactions: Order Entry, Item in Stock Search, Browse Order Status, Update Account, and Purchase from Stock. The transactions are being executed from agent computers 40 located in four geographic regions: New York, Japan, United Kingdom and San Francisco. More than one agent computer may be used in each such location. The names and granularities of the geographic locations can be defined by the operator during the setup process.
The graphs indicate various aspects of the transactional server's performance as monitored over a particular time frame (the current day in this example). The first graph 76 (Figure 13) shows the minimum, average, and maximum transaction times for each of the five transactions. The second graph 78 (Figure 13) shows the average response time for each transaction and each one-hour interval, using a color coding scheme to distinguish between the transactions. The third graph 80 (Figure 14) shows the distribution of service levels for each of the five transactions, using a unique color for each level. The fourth graph 82 shows, for each one-hour interval and each transaction, the percentage of transactions that failed. As illustrated in Figure 13, the report pages preferably include various links and controls for allowing the user to generate customized and attribute filtered views of the performance data For example, if the user selects the "drill down" link for the "browse order status" transaction, a page appears which includes the graphs 84, 86 shown in Figure 15 Both graphs 84, 86 shows aspects of the server response time for the Browse Order Status transaction broken down by location, as may be desirable to identify location dependent problems The horizontal line in these graphs 84, 86 represents a user defined alert threshold. From this page, the user can drill down an additional level (by selecting the location specific drill down links 90) to view location specific graphs for the Browse Order Status transaction.
With further reference to Figures 13 15, the "Report Parameters" window 86 allows the user to modify the time frame and/or the breakdown method used to generate the various graphs and charts By modifying the breakdown method, the user can view the performance data separately for each transaction and for each attribute of the agent computers. In one embodiment, the performance data can be viewed by transaction (shown in Figures 13 and 14), by location (shown in Figure 15), by organization (not illustrated), and by ISP (not illustrated). In other embodiments, the performance data can be broken down according to other attribute types, including attribute types defined by the operator.
The "Filters" option 88 (Figures 13 15) allows the user to filter the displayed information by transaction and by each of the attributes. Using this feature, the user can, for example, filter out from the reports the performance data corresponding to a particular transaction, location, organization, ISP, or combination thereof. In one embodiment (not shown), the user specifies the filter to be applied by completing a web form that includes a respective check box for each transaction and each attribute used in the monitoring session The application of a filter, if any, is indicated by the notations at the tops of the graphs (e.g., "Transactions: All; Locations: UK, NY, Organizations: accounting, marketing").
The Graph List option 90 allows the user to specify the set of default graphs that are to appear on the main status reports page. The "Settings" option 92 allows the user to adjust and save other types of settings, such as an "auto refresh" rate (e.g., every five minutes) and a starting date/time to be used within the reports.
Figure 16 illustrates an example "Transaction Health Distribution" chart that may be generated by the reports server 36. In this example, the chart is being viewed through the browser window of the controller's interface. The chart is in the form of a 2 dimensional matrix. The horizontal dimension represents the timeframe, which can be modified by the user over a range of hours to years In this example, the columns represent hours of the current day (as displayed along the top of the chart), and the rows represent the transactions being monitored (as listed at the left). The cells of the matrix are color coded to reflect the response time of the particular transaction during in the particular time frame. Each hour and each transaction is a hyperlink that, when selected, causes the view to change. For example, if the user clicks on a particular hour, the timeframe changes to just that hour with the matrix's horizontal dimension broken down into smaller (e.g., 5 or 10 minute) intervals. Similarly, when the user clicks on a transaction link, the vertical dimension changes so that the chart shows only the selected transaction, broken down according to geographical location (or possibly another computer attribute).
As will be apparent from the foregoing examples, the ability to separately view and filter the performance data based on the attributes of the agent computers, including operator specified attributes, greatly simplifies the task of identifying attribute-specific problems. Although specific attribute types are shown in the example reports, it should be understood that the illustrated features can be applied to other types of attributes, including user assigned attribute types.
The reports server 36 also preferably provides access to an Alerts chart (not shown) which contains information about the various alert events that have occurred. For each alert event, this chart may include, for example, an alert name, a color-coded indication of the alert severity, the time of the alert event, the action taken (e.g.,
"email sent to admιn merc int.com" or "logged only"), and the text of any alert message sent.
VI. Data Flow and Database Content
The general flow of information between components during the setup and execution of a typical monitoring session will now be described with reference to Figures 17-19. Figure 17 illustrates the "setup" or "programming" phase of a monitoring session. As depicted by the left-to- πght arrows in Figure 17, once the user completes the setup process, the controller 34 dispatches the testcases
(transactions) and schedules to the respective agents 32. Where the agents 32 reside on remote agent computers 40, the testcases and schedules are communicated over the Internet using HTTP or another a TCP/IP based protocol via
API calls. As further depicted by Figure 17, the controller also sends session configuration data to the reports server 36 (preferably using HTTP) for storage in the sessions database 42. The configuration data includes the session name, identifiers and properties (attributes) of the agent computers 40, and identifiers and names of the transactions. Where the reports server 36 services multiple business entities, the configuration data may also include a username or other identifier of the business entity to which the session corresponds.
Table 1 summarizes, for one example embodiment, the tables that are created in the sessions database 42 for each monitoring session and used to generate the reports. Any of a variety of alternative database schemas could be used. The various metrics that are displayed in the reports (e.g , average response time over a particular window) are calculated using the data stored in the event meter table.
Figure imgf000017_0001
TABLE 1 - EXAMPLE DATABASE SCHEMA
As depicted by the downward arrow in Figure 17, any alerts set up by the user are stored in local storage 38 along with session configuration data. The alerts may additionally or alternatively be communicated to the reports server 36, in which case the reports server may handle the task of checking for and notifying users of alert conditions.
Figure 18 illustrates the flow of data for a representative, remote agent 32 as the agent executes a testcase.
During the execution process, the agent 32 interacts with (e.g., sends HTTP Post and Get messages to) the transactional server 30 while monitoring one or more predefined performance parameters such as response time. The agent 32 also checks any verification points (e.g., expected values or text strings) defined within the testcase. Upon completing each transaction, the agent 32 sends the resulting transaction execution data to the controller 34 using HTTP or another TCP/IP based protocol. The transaction execution data preferably includes a transaction ID, the performance data (response time and pass/fail status) for the transaction, a transaction time/date stamp, and the host ID of the agent computer 40. The agents could alternatively be designed to report their execution on a more or less frequent basis (e.g., once per server response, or once per testcase execution). The controller 34 compares the performance data to any predefined alert conditions. If an alert condition is satisfied for which a notification message has been defined, the controller sends an alert notification message (represented by a dashed line in Figure 18) to the appropriate entity. Upon receiving an alert notification message, the recipient can log into the reports server 36 to obtain details of the alert event, such as the location or organization of the agent computer that reported associated performance data. The alert events could also be stored locally to the controller computer and displayed within the session tree 46. As further depicted by Figure 18, the controller 34 forwards the transaction execution data and any satisfied alert conditions to the web reports server 36 (preferably using the HTTP protocol) for insertion into the sessions database 42. As with the agent-to controller communications, the controller preferably forwards the transaction execution data to the reports server 36 substantially in real time, on a transaction by transaction basis. This is accomplished in the preferred embodiment through an API of the automation interface 34C (Figure 1 ). The alert events are detected and reported to the reports server 36 in real-time by the alerts engine 34D. If multiple agents 32 are scheduled to execute testcases concurrently, the controller 34 processes the data streams from the multiple agents concurrently. The main controller loop is thus in the form of:
wait for message from a Vuser (agent) route message to web reports server via API call
ApmApι_reportTransactιon(transactιon, host, status, value) route message to alarms engine
Various alternatives to the data flow process shown in Figure 18 are possible. For example, the agents 32 could send the transaction execution data directly to the reports server 36, in which case the reports server 30 could optionally forward some or all of the execution data (e.g., alert conditions only) to the controller 34. In addition, all agent computers 40 within a given location or organization could be configured to aggregate their performance data for transmission to or retrieval by the controller 34 or the reports server 36. In addition, the task of checking for and notifying users of alert conditions could be performed by the agents 32 and/or by the reports server 30, rather than by the controller 34. Further, the agents 32 could be configured to "filter" the transaction execution data, so that only those transactions that meet certain predefined criteria are reported. These and other alternatives could optionally be provided as user-configurable options. Figure 19 illustrates the process of remotely accessing the sessions database 42 using a standard web browser 100. As illustrated, the user initially logs into his or her account using a username/password combination or other authentication method. Thereafter, the user views customized, real-time status reports (as described above) for the transaction server or servers corresponding to that account. As the reports pages are requested, the database 42 is accessed and the various performance metrics calculated using programming methods that are well known by those skilled in the art.
VII. Additional Features for Detecting and Reporting Problems
Three optional features for detecting and reporting error conditions and performance problems will now be described. All three of these features are preferably implemented in part through executable code of the agent component 32. The first such feature involves having the agent computers 40 capture the screens returned by the transactional server 30 during transaction execution, and then forward these screen captures to the reports server 36 if the transaction is unsuccessful. When the end user drills down on a failed transaction within a report, the reports server 36 displays, or presents an option to display, the captured sequence of screen displays for the failed transaction. For example, if the failed transaction involved an unexpected or missing message on a web page, the user could view the entire web page as well as the web pages (including any form data submitted by the agent) that preceded the unexpected response. An important benefit of this feature is the ability for the user to view the sequence of events that led to the failed transaction.
Figure 20 illustrates the screen capture process as implemented within the agent component 32. As depicted by blocks 110-1 16, each time the agent 32 submits a request to the transactional server 30, the agent captures the screen returned by the transactional server and compares this response against any associated verification points defined within the transaction. The screen displays are preferably stored as bitmap images, but may alternatively be stored in another format such as HTML documents and associated objects.
Once the transaction is finished, the agent 32 determines whether the transaction completed successfully. A transaction is preferably treated as unsuccessful if any verification point failed. A transaction may also be treated as unsuccessful if, for example, a timeout event occurred. In the event of a transaction failure, the agent 32 sends the sequence of captured screen displays to the reports server 36 (block 120), which in turn stores the screen displays in the sessions database 42 for later viewing. The screen displays could additionally or alternatively be sent by email to a human operator for viewing. If the transaction completes successfully, the screen displays are discarded without being forwarded to the reports server 36.
A second feature that may be incorporated into the agent 32 is an ability to measure and report segment delays incurred along a network path between an agent computer 40 and the transactional server 30. The segment delays are preferably measured using the Network Monitor component of the commercially-available LoadRunner 6.0 product of Mercury Interactive Corporation. Preferably, some or all of the agents 32 are configured via the controller 34 to launch the Network Monitor (on their respective agent computers 40) when the path delay exceeds a preprogrammed threshold. These thresholds may optionally be specified by the user when setting up a monitoring session. Upon being launched, the Network Monitor measures the delay along each segment of the path between the relevant agent computer 40 and the transactional server 30 using well-known methods. The agent 32 then reports these measurements to the reports server 36, which allows the user to drill down and view the measurements. The measured delays are preferably presented using the standard segment delay and path delay graphs provided within
LoadRunner 6.0. The segment delay data may be used, for example, to detect router problems or bottlenecks in network architectures.
A third feature involves the ability of the agents 32 to detect and report "broken links" (links to inaccessible files or other objects) within web sites. Using this feature, the user can remotely program one or more of the agent computers 40 to crawl the web site periodically (e.g., once per day) to check for broken links, and to report any broken links that are found. When broken links are located, a list of the broken links may automatically be posted to the reports server 36 for viewing and/or be sent to the user by email. Each broken link may be reported to the user in the form of a URL pair that indicates the respective locations of the missing object and the page containing the broken link. Techniques for crawling web sites and checking for broken links are well known in the art, and are described, for example, in U.S. Patent No. 5,958,008 of Mercury Interactive Corporation As with other types of problems detected by the agents 32, when a particular object is accessible from some agent computers 40 but not others, the reports server 40 preferably allows the user to separately view the attributes of the agent computers that experienced the problem.
Although the invention has been described in terms of certain preferred embodiments, other embodiments that are apparent to those of ordinary skill in the art, including embodiments which do not provide all of the features and advantages set forth herein, are also within the scope of this invention. Accordingly, the scope of the invention is defined by the claims that follow. In the method claims, reference characters are used for convenience of description only, and do not indicate a particular order for performing the method.

Claims

WHAT IS CLAIMED IS:
1. A method for monitoring the performance of a deployed transactional server, comprising the steps of:
(a) programming a plurality of computers to execute transactions on the deployed transactional server as simulated users while monitoring performance of the transactional server;
(b) assigning attributes to the plurality of computers such that at least some of the computers have different attributes than others;
(c) receiving and storing performance data generated by the plurality of computers as a result of step (a), the performance data indicating at least one parameter of the performance of the transactional server; and
(d) displaying the performance data separately for each of multiple attributes assigned in step (b).
2. The method as in Claim 1, wherein step (d) comprises generating a report which separately indicates the performance of the transactional server as monitored from each of multiple geographic locations.
3. The method as in Claim 1, wherein step (d) comprises generating a report which separately indicates the performance as monitored from each multiple organizations.
4. The method as in Claim 1, wherein step (d) comprises generating a report which separately indicates the performance as monitored through each of multiple Internet service providers.
5. The method as in Claim 1, wherein step (a) comprises assigning automated execution schedules to the plurality of computers, wherein the execution schedules specify timing for executing the transactions.
6. The method as in Claim 1 , wherein step (a) comprises programming at least some of the plurality of computers to verify user-selected content of responses from the transactional server.
7. The method as in Claim 1, wherein step (a) comprises programming at least some of the plurality of computers remotely using a controller program that dispatches testcases to the computers.
8. The method as in Claim 7, wherein the controller program is hosted on a server as a web based service.
9. The method as in Claim 1, further comprising generating and transmitting an alert message when the performance data satisfies an alert condition.
10. The method as in Claim 9, wherein the alert condition is specific to an attribute specific subset of the plurality of computers.
11. The method as in Claim 1 , wherein step (c) comprises receiving and storing the performance data substantially in real time as transactions are executed.
12. The method as in Claim 1, further comprising programming the transactional server to process a destructive transaction executed by the one or more of the plurality of computers non destructively.
13. The method as in Claim 1 , wherein at least some of the plurality of computers are computers used by end users of the transactional server.
14. The method as in Claim 1 , wherein the performance data comprises a sequence of screen displays returned by the transactional server during a failed transaction.
15. The method as in Claim 1, wherein the performance data comprises network segment delays measured by one or more of the plurality of computers.
16. The method as in Claim 1, wherein the performance data comprises identifiers of broken web site links detected by one or more of the plurality of computers.
17. A computer-readable medium having a controller program stored thereon which, when executed by a computer, provides functions for at least: selecting a plurality of computers to include within a monitoring session for monitoring the post- deployment operation of a transactional server; assigning transactions to the plurality of computers for exercising and monitoring the transactional server; and assigning attributes to specific computers of the plurality of computers to permit monitoring of the transactional server separately for each of a plurality of attributes.
18. The computer-readable medium as in Claim 17, wherein the attributes include names of organizations in which the computers are located.
19. The computer-readable medium as in Claim 17, wherein the attributes include names of geographic regions in which the computers are located.
20. The computer-readable medium as in Claim 17, wherein the attributes include at least one of (a) Internet Service Providers used by the computers, and (b) routers to which the computers are coupled.
21. The computer-readable medium as in Claim 17, wherein the attributes include configurations of the computers.
22. The computer-readable medium as in Claim 17, wherein the controller program provides an option to assign different transactions to different computers of the plurality.
23. The computer readable medium as in Claim 17, wherein the controller program provides a function for assigning execution schedules to the plurality of computers for executing the transactions.
24. The computer-readable medium as in Claim 23, wherein the controller program provides an option for the user to define the execution schedules.
25. The computer-readable medium as in Claim 17, wherein the controller program graphically represents the monitoring session to the user as a tree in which the transactions are represented as children of corresponding computers.
26. The computer-readable medium as in Claim 25, wherein the controller program further represents execution schedules that are assigned to the computers as respective children in the tree.
27. The computer-readable medium as in Claim 17, in combination with a report server component that uses the assigned attributes to separate transactional server performance data for display.
28. The computer-readable medium as in Claim 17, in combination with an agent component which is adapted to be installed on the plurality of computers to permit the computers to be remotely programmed by the controller program.
29. The computer-readable medium as in Claim 17, wherein the controller program provides a user option to specify an alert condition.
30. The computer-readable medium as in Claim 29, wherein the controller program provides an option to define an alert condition that is specific to a subset of the plurality of attributes.
31. The computer-readable medium as in Claim 17, wherein the controller program implements functions for dispatching the transactions to the plurality of computers.
32. The computer-readable medium as in Claim 17, wherein the controller program includes functions for recording the transactions.
33. The computer-readable medium as in Claim 17, wherein the controller program includes functions for the user to specify expected responses from the transactional server.
34. A method for monitoring a deployed transactional server, comprising: remotely programming a group of computers to access the deployed transactional server as simulated users while monitoring performance of the transactional server such that the transactional server is monitored substantially continuously by the group; monitoring performance data generated by the group substantially in real-time to check for an alert condition; and generating an alert notification message in response to detection of the alert condition .
35. The method as in Claim 34, wherein the alert condition is specific to an attribute-based subset of computers of the group.
36. The method as in Claim 34, further comprising storing the performance data in a database substantially in real-time, and providing remote, online access to the database.
37. The method as in Claim 36, wherein providing online access comprises providing a user option to specify a timeframe over which to view the performance data.
38. The method as in Claim 34, wherein the group includes computers of end-users of the transactional server.
39. A method of monitoring the operation of a transactional server, comprising: installing an agent component on a plurality of computers, including computers of end users of the transactional server, wherein the agent component is adapted to execute transactions as simulated users of the transactional server while monitoring performance of the transactional server; and remotely assigning to the plurality of computers the transactions to be executed by the agent components installed thereon.
40. The method as in Claim 39, wherein assigning the transactions comprises selecting, on a computer- by-computer basis, the transactions to be assigned to each of the plurality of computers.
41. The method as in Claim 40, further comprising remotely assigning execution schedules to the plurality of computers for executing the transactions.
42. The method as in Claim 41 , wherein assigning the execution schedules comprises specifying, on a computer-by-computer basis, the execution schedule to be used by each of the plurality of computers.
43. The method as in Claim 39, further comprising aggregating and providing remote access to performance data collected by the plurality of computers, the performance data indicating performance of the transactional server.
44. The method as in Claim 43, wherein the performance data includes a sequence of screen displays captured by at least one of the plurality of computers during execution of a transaction.
45. The method as in Claim 43, wherein the performance data includes network path segment delays measured by at least one of the plurality of computers.
46. The method as in Claim 43, wherein the performance data includes identifiers of broken web site links detected by at least one of the plurality of computers.
47. A method of monitoring operation of a transactional server, comprising, on each of a plurality of computers that are programmed to monitor the transactional server as simulated users: executing a transaction as a simulated user of the transactional server; during transaction execution, storing a sequence of screens displays returned by the transactional server; determining whether the transaction completed successfully; and if the transaction did not complete successfully, forwarding the sequence of screen displays to a server for subsequent viewing.
PCT/US2000/024303 1999-09-01 2000-08-31 Post-deployment monitoring of server performance WO2001016753A2 (en)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP00959879A EP1214657A2 (en) 1999-09-01 2000-08-31 Post-deployment monitoring of server performance
JP2001520640A JP2003508849A (en) 1999-09-01 2000-08-31 Post-deployment monitoring of server performance
CA002380358A CA2380358A1 (en) 1999-09-01 2000-08-31 Post-deployment monitoring of server performance
AU71123/00A AU763468B2 (en) 1999-09-01 2000-08-31 Post-deployment monitoring of server performance

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US15182499P 1999-09-01 1999-09-01
US60/151,824 1999-09-01
US09/484,686 2000-01-17
US09/484,686 US6449739B1 (en) 1999-09-01 2000-01-17 Post-deployment monitoring of server performance

Publications (2)

Publication Number Publication Date
WO2001016753A2 true WO2001016753A2 (en) 2001-03-08
WO2001016753A3 WO2001016753A3 (en) 2001-11-29

Family

ID=26849002

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2000/024303 WO2001016753A2 (en) 1999-09-01 2000-08-31 Post-deployment monitoring of server performance

Country Status (6)

Country Link
US (2) US6449739B1 (en)
EP (1) EP1214657A2 (en)
JP (1) JP2003508849A (en)
AU (1) AU763468B2 (en)
CA (1) CA2380358A1 (en)
WO (1) WO2001016753A2 (en)

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2002079909A2 (en) 2001-03-30 2002-10-10 Bmc Software, Inc. Synthetic transaction monitor
WO2003005202A1 (en) 2001-07-06 2003-01-16 Computer Associates Think, Inc. Method and system for providing a virtual user interface
JP2003030060A (en) * 2001-07-19 2003-01-31 Hitachi Electronics Service Co Ltd Performance monitoring service system for web server
WO2003023621A2 (en) * 2001-09-10 2003-03-20 Mercury Interactive Corporation Network-based control center for conducting performance tests of server systems
WO2003038550A2 (en) * 2001-10-26 2003-05-08 Capital One Financial Corporation Systems and methods for table driven automation testing of software programs
EP1384153A2 (en) * 2001-05-04 2004-01-28 Netqos, Inc. Server-site response time computation for arbitrary applications
EP1386240A2 (en) * 2001-03-30 2004-02-04 BMC Software, Inc. Synthetic transaction monitor
US7437450B1 (en) * 2001-11-30 2008-10-14 Cisco Technology Inc. End-to-end performance tool and method for monitoring electronic-commerce transactions
WO2009068642A1 (en) * 2007-11-30 2009-06-04 International Business Machines Corporation Method for using dynamically scheduled synthetic transactions to monitor performance and availability of e-business systems
EP2198398A1 (en) * 2007-08-28 2010-06-23 Sugarcrm Inc. Crm system and method having drilldowns, acls, shared folders, a tracker and a module builder
US7792948B2 (en) 2001-03-30 2010-09-07 Bmc Software, Inc. Method and system for collecting, aggregating and viewing performance data on a site-wide basis
GB2491015A (en) * 2011-05-17 2012-11-21 Ibm Installing and testing an application on a highly utilized computer platform
US10884892B2 (en) 2017-06-28 2021-01-05 Fujitsu Limited Non-transitory computer-readable storage medium, display control method and display control device for observing anomolies within data

Families Citing this family (258)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6108637A (en) 1996-09-03 2000-08-22 Nielsen Media Research, Inc. Content display monitor
US6973490B1 (en) * 1999-06-23 2005-12-06 Savvis Communications Corp. Method and system for object-level web performance and analysis
US6449739B1 (en) 1999-09-01 2002-09-10 Mercury Interactive Corporation Post-deployment monitoring of server performance
US7290056B1 (en) * 1999-09-09 2007-10-30 Oracle International Corporation Monitoring latency of a network to manage termination of distributed transactions
US7206805B1 (en) 1999-09-09 2007-04-17 Oracle International Corporation Asynchronous transcription object management system
US6772107B1 (en) * 1999-11-08 2004-08-03 J.D. Edwards World Source Company System and method for simulating activity on a computer network
US6883120B1 (en) * 1999-12-03 2005-04-19 Network Appliance, Inc. Computer assisted automatic error detection and diagnosis of file servers
US7013251B1 (en) * 1999-12-15 2006-03-14 Microsoft Corporation Server recording and client playback of computer network characteristics
US7373376B1 (en) * 1999-12-30 2008-05-13 Keynote Systems, Inc. Method and system for evaluating quality of service over the internet
US6662226B1 (en) * 2000-01-27 2003-12-09 Inbit, Inc. Method and system for activating and capturing screen displays associated with predetermined user interface events
US8510437B2 (en) * 2000-01-27 2013-08-13 Yawonba Holdings Au, Llc Method and system for tracking screen activities
US7299281B1 (en) 2000-01-27 2007-11-20 Inbit, Inc. Method and system for activating and capturing screen displays associated with predetermined user interface events
US20030126258A1 (en) * 2000-02-22 2003-07-03 Conkright Gary W. Web based fault detection architecture
US7281040B1 (en) * 2000-03-07 2007-10-09 Cisco Technology, Inc. Diagnostic/remote monitoring by email
US7249192B1 (en) * 2000-03-09 2007-07-24 Hewlett-Packard Development Company, L.P. Protocol for insuring exactly once semantics of transactions across an unordered, unreliable network
US6892236B1 (en) * 2000-03-16 2005-05-10 Microsoft Corporation System and method of generating computer system performance reports
US6973489B1 (en) * 2000-03-21 2005-12-06 Mercury Interactive Corporation Server monitoring virtual points of presence
US7260837B2 (en) * 2000-03-22 2007-08-21 Comscore Networks, Inc. Systems and methods for user identification, user demographic reporting and collecting usage data usage biometrics
US7930285B2 (en) * 2000-03-22 2011-04-19 Comscore, Inc. Systems for and methods of user demographic reporting usable for identifying users and collecting usage data
US7111205B1 (en) * 2000-04-18 2006-09-19 Siemens Communications, Inc. Method and apparatus for automatically reporting of faults in a communication network
US7120676B2 (en) 2000-04-28 2006-10-10 Agilent Technologies, Inc. Transaction configuration system and method for transaction-based automated testing
US7523180B1 (en) * 2000-04-28 2009-04-21 Microsoft Corporation System and method for service chain management in a client management tool
US6941339B1 (en) * 2000-05-17 2005-09-06 Unbound Technologies Inc. Stated network portal system and method
US20030009544A1 (en) * 2000-06-05 2003-01-09 Wach Raymond S. Method of performing distributed load testing
US7412501B2 (en) * 2000-06-07 2008-08-12 Microsoft Corporation Event consumers for an event management system
CN1496499A (en) * 2000-06-09 2004-05-12 ͨ�õ�����˾ System and method for utility enterprise management
US6665822B1 (en) * 2000-06-09 2003-12-16 Cisco Technology, Inc. Field availability monitoring
EP1352332A4 (en) * 2000-06-21 2004-12-08 Concord Communications Inc Liveexception system
US6868539B1 (en) * 2000-06-28 2005-03-15 Microsoft Corp. System and method providing single application image
US6961681B1 (en) * 2000-09-12 2005-11-01 Microsoft Corporation System and method providing virtual applications architecture
US7278103B1 (en) * 2000-06-28 2007-10-02 Microsoft Corporation User interface to display and manage an entity and associated resources
US6785666B1 (en) * 2000-07-11 2004-08-31 Revenue Science, Inc. Method and system for parsing navigation information
US6799213B1 (en) * 2000-08-31 2004-09-28 Sprint Communications Company, L.P. System and method for performing interactive server load testing through use of one or more virtual users being configured as a server client capable of transmitting one or more server test actions
US20020116491A1 (en) * 2000-09-01 2002-08-22 Boyd Eric L. Method and system for probing a network
AU9268901A (en) * 2000-09-15 2002-03-26 Wonderware Corp An industrial process control data access server supporting multiple client dataexchange protocols
US6836773B2 (en) * 2000-09-28 2004-12-28 Oracle International Corporation Enterprise web mining system and method
US7117208B2 (en) * 2000-09-28 2006-10-03 Oracle Corporation Enterprise web mining system and method
US7287071B2 (en) * 2000-09-28 2007-10-23 Vignette Corporation Transaction management system
US8145742B1 (en) * 2000-10-31 2012-03-27 Red Hat, Inc. Method of and apparatus for network administration
US6950868B1 (en) * 2000-10-31 2005-09-27 Red Hat, Inc. Method of and apparatus for remote monitoring
US7032015B1 (en) 2000-10-31 2006-04-18 General Electric Company System and method for integrating a power system over a network
CA2327211A1 (en) * 2000-12-01 2002-06-01 Nortel Networks Limited Management of log archival and reporting for data network security systems
AU2002230735A1 (en) * 2000-12-11 2002-06-24 Phlair, Inc. System and method for detecting and reporting online activity using real-time content-based network monitoring
WO2002048924A2 (en) * 2000-12-12 2002-06-20 Uri Wilensky Distributed agent network using object based parallel modeling language to dynamically model agent activities
US7937470B2 (en) * 2000-12-21 2011-05-03 Oracle International Corp. Methods of determining communications protocol latency
US7577701B1 (en) 2001-01-22 2009-08-18 Insightete Corporation System and method for continuous monitoring and measurement of performance of computers on network
AU2002250146A1 (en) * 2001-02-28 2002-09-19 Wily Technology, Inc. Detecting a stalled routine
US7082465B1 (en) * 2001-03-27 2006-07-25 Cisco Technology, Inc. Web based management of host computers in an open protocol network
US20040205489A1 (en) * 2001-04-09 2004-10-14 Ncr Corporation Operation of web sites on internet
US7260827B1 (en) * 2001-04-23 2007-08-21 Unisys Corporation Manual mode method of testing a video server for a video-on-demand system
US6961766B2 (en) * 2001-04-24 2005-11-01 Oracle International Corp. Method for extracting personalization information from web activity
US20020170004A1 (en) * 2001-05-08 2002-11-14 Shugart Technology, Inc. Storage area network monitor device and networked monitor system
US20020169863A1 (en) * 2001-05-08 2002-11-14 Robert Beckwith Multi-client to multi-server simulation environment control system (JULEP)
US20020198985A1 (en) * 2001-05-09 2002-12-26 Noam Fraenkel Post-deployment monitoring and analysis of server performance
US6738933B2 (en) 2001-05-09 2004-05-18 Mercury Interactive Corporation Root cause analysis of server system performance degradations
US7197559B2 (en) * 2001-05-09 2007-03-27 Mercury Interactive Corporation Transaction breakdown feature to facilitate analysis of end user performance of a server system
US7197557B1 (en) * 2001-05-29 2007-03-27 Keynote Systems, Inc. Method and system for evaluating quality of service for streaming audio and video
US6874099B1 (en) * 2001-05-31 2005-03-29 Sprint Communications Company L.P. Method and software for testing and performance monitoring
US7546354B1 (en) * 2001-07-06 2009-06-09 Emc Corporation Dynamic network based storage with high availability
US7424526B1 (en) * 2001-07-31 2008-09-09 Sprint Communications Company L.P. Internet service node incorporating a bandwidth measurement device and associated methods for evaluating data transfers
GB0118665D0 (en) * 2001-07-31 2001-09-19 Hewlett Packard Co Remote monitoring of computer devices
US7111204B1 (en) * 2001-08-01 2006-09-19 Agilent Technologies, Inc. Protocol sleuthing system and method for load-testing a network server
US6963874B2 (en) * 2002-01-09 2005-11-08 Digital River, Inc. Web-site performance analysis system and method utilizing web-site traversal counters and histograms
CA2455079A1 (en) * 2001-08-06 2003-02-20 Mercury Interactive Corporation System and method for automated analysis of load testing results
US6871293B2 (en) * 2001-08-07 2005-03-22 American Management Systems, Inc. Gap detector detecting gaps between transactions transmitted by clients and transactions processed by servers
JP4294912B2 (en) 2001-08-13 2009-07-15 ブラザー工業株式会社 Terminal information notification system, terminal information notification method, and network terminal device
US6961769B2 (en) * 2001-09-20 2005-11-01 International Business Machines Corporation Method, apparatus, and program for measuring server performance using multiple clients
US7257516B2 (en) * 2001-09-20 2007-08-14 International Business Machines Corporation Method, apparatus, and program for eliminating thread skew in multithreaded performance benchmarks
US7552056B2 (en) 2001-09-25 2009-06-23 Emc Corporation Scalable storage service registration application
US8055555B2 (en) * 2001-09-25 2011-11-08 Emc Corporation Mediation device for scalable storage service
US7376730B2 (en) * 2001-10-10 2008-05-20 International Business Machines Corporation Method for characterizing and directing real-time website usage
US20030097445A1 (en) * 2001-11-20 2003-05-22 Stephen Todd Pluggable devices services and events for a scalable storage service architecture
US7035922B2 (en) * 2001-11-27 2006-04-25 Microsoft Corporation Non-invasive latency monitoring in a store-and-forward replication system
US8549048B2 (en) * 2001-12-19 2013-10-01 Emc Corporation Workflow database for scalable storage service
US20030128231A1 (en) * 2002-01-09 2003-07-10 Stephane Kasriel Dynamic path analysis
US7631035B2 (en) * 2002-01-09 2009-12-08 Digital River, Inc. Path-analysis toolbar
US20030131097A1 (en) * 2002-01-09 2003-07-10 Stephane Kasriel Interactive path analysis
US8527620B2 (en) 2003-03-06 2013-09-03 International Business Machines Corporation E-business competitive measurements
US7269651B2 (en) * 2002-09-26 2007-09-11 International Business Machines Corporation E-business operations measurements
US8086720B2 (en) 2002-01-31 2011-12-27 International Business Machines Corporation Performance reporting in a network environment
US7043549B2 (en) * 2002-01-31 2006-05-09 International Business Machines Corporation Method and system for probing in a network environment
US7047291B2 (en) 2002-04-11 2006-05-16 International Business Machines Corporation System for correlating events generated by application and component probes when performance problems are identified
US7412502B2 (en) * 2002-04-18 2008-08-12 International Business Machines Corporation Graphics for end to end component mapping and problem-solving in a network environment
US7130902B2 (en) * 2002-03-15 2006-10-31 Ge Mortgage Holdings, Llc Methods and apparatus for detecting and providing notification of computer system problems
US20030202009A1 (en) * 2002-04-24 2003-10-30 Stephane Kasriel Integration toolbar
US7490148B1 (en) 2002-05-30 2009-02-10 At&T Intellectual Property I, L.P. Completion performance analysis for internet services
US7159148B2 (en) * 2002-06-11 2007-01-02 Motorola, Inc. Method for performance and fault management in a telecommunication network
US20030233446A1 (en) * 2002-06-12 2003-12-18 Earl William J. System and method for managing a distributed computing system
US20030233453A1 (en) * 2002-06-18 2003-12-18 Institute For Information Industry Topology probing method for mobile IP system
US7877435B2 (en) * 2002-06-20 2011-01-25 International Business Machines Corporation Method and system for transaction pipeline decomposition
US8266270B1 (en) 2002-07-16 2012-09-11 At&T Intellectual Property I, L.P. Delivery performance analysis for internet services
US7310798B1 (en) 2002-08-19 2007-12-18 Sprint Communications Company L.P. Simulator tool for testing software in development process
US7640342B1 (en) * 2002-09-27 2009-12-29 Emc Corporation System and method for determining configuration of one or more data storage systems
US20040064531A1 (en) * 2002-10-01 2004-04-01 Wisner Steven P. System and process for projecting hardware requirements for a web site
US6792460B2 (en) * 2002-10-02 2004-09-14 Mercury Interactive Corporation System and methods for monitoring application server performance
US7216164B1 (en) * 2002-10-09 2007-05-08 Cisco Technology, Inc. Methods and apparatus for determining the performance of a server
US7870431B2 (en) * 2002-10-18 2011-01-11 Computer Associates Think, Inc. Transaction tracer
US7353264B2 (en) * 2002-11-13 2008-04-01 Hewlett-Packard Development Company, L.P. Method and apparatus for optimizing client responsiveness and server performance
US7346678B1 (en) * 2002-11-14 2008-03-18 Web Ex Communications, Inc. System and method for monitoring and managing a computing service
US7885974B2 (en) 2002-11-18 2011-02-08 Aol Inc. Method and apparatus providing omnibus view of online and offline content of various file types and sources
US7457864B2 (en) * 2002-11-27 2008-11-25 International Business Machines Corporation System and method for managing the performance of a computer system based on operational characteristics of the system components
US20040199618A1 (en) * 2003-02-06 2004-10-07 Knight Gregory John Data replication solution
US8726075B1 (en) * 2003-02-14 2014-05-13 At&T Intellectual Property Ii, L.P. Method and apparatus for screenshot archiving to digital video disk (DVD)
US20040205184A1 (en) * 2003-03-06 2004-10-14 International Business Machines Corporation E-business operations measurements reporting
EP1614254A1 (en) * 2003-04-04 2006-01-11 Computer Associates Think, Inc. Method and system of alert notification
US7155641B2 (en) * 2003-05-15 2006-12-26 Microsoft Corporation System and method for monitoring the performance of a server
US7627669B2 (en) * 2003-05-21 2009-12-01 Ixia Automated capturing and characterization of network traffic using feedback
JP4276895B2 (en) * 2003-05-26 2009-06-10 株式会社日立製作所 Measuring system
US7337176B1 (en) 2003-08-29 2008-02-26 Sprint Communications Company L.P. Data loading tool for loading a database
US7472184B2 (en) * 2003-09-19 2008-12-30 International Business Machines Corporation Framework for restricting resources consumed by ghost agents
US7493387B2 (en) * 2003-09-19 2009-02-17 International Business Machines Corporation Validating software in a grid environment using ghost agents
US7493386B2 (en) * 2003-09-19 2009-02-17 International Business Machines Corporation Testing applications within a grid environment using ghost agents
WO2005043300A2 (en) * 2003-10-20 2005-05-12 Empirix, Inc. Computer language interpretation and optimization for server testing
US7337431B1 (en) 2003-12-23 2008-02-26 Sprint Communications Company L.P. Distributed large-scale application benchmark system
KR100599936B1 (en) * 2003-12-24 2006-07-13 한국전자통신연구원 Virtual Environment Network User Simulator System
US7328134B1 (en) 2004-02-26 2008-02-05 Sprint Communications Company L.P. Enterprise integration test tool
WO2005083571A1 (en) * 2004-03-01 2005-09-09 Izuki Corporation A method of controlling the operation of a computing system arranged to interact with other entities
US7216256B2 (en) 2004-03-30 2007-05-08 Bellsouth Intellectual Property Corporation Methods, systems, and products for verifying integrity of web-server served content
US7363364B2 (en) * 2004-03-30 2008-04-22 At&T Delaware Intellectual Property, Inc. Methods, systems, and products for verifying integrity of web-server served content
US7426556B2 (en) 2004-03-30 2008-09-16 At&T Intellectual Property I, L.P. Methods, systems, and products for verifying integrity of web-server served content
US7685273B1 (en) * 2004-03-31 2010-03-23 Compuware Corporation Methods and apparatus for collecting and displaying performance metrics from a web site
US8065410B1 (en) * 2004-03-31 2011-11-22 Compuware Corporation Methods and apparatus for collecting performance metrics from a web site
US20060031521A1 (en) * 2004-05-10 2006-02-09 International Business Machines Corporation Method for early failure detection in a server system and a computer system utilizing the same
US8180864B2 (en) * 2004-05-21 2012-05-15 Oracle International Corporation System and method for scripting tool for server configuration
US7509343B1 (en) * 2004-06-09 2009-03-24 Sprint Communications Company L.P. System and method of collecting and reporting system performance metrics
US7290205B2 (en) * 2004-06-23 2007-10-30 Sas Institute Inc. System and method for management of document cross-reference links
US20060031469A1 (en) * 2004-06-29 2006-02-09 International Business Machines Corporation Measurement, reporting, and management of quality of service for a real-time communication application in a network environment
US7346807B1 (en) 2004-07-07 2008-03-18 Sprint Communications Company L.P. Optimizing transaction data for load testing
US7133805B1 (en) 2004-07-07 2006-11-07 Sprint Communications Company L.P. Load test monitoring system
US20060020699A1 (en) * 2004-07-23 2006-01-26 D Esposito John J Method and computer program for web site performance monitoring and testing by variable simultaneous angulation
US20060064399A1 (en) * 2004-09-21 2006-03-23 Giuseppe De Sio Method and system for testing distributed software applications
KR100813395B1 (en) 2004-09-24 2008-03-12 주식회사 케이티 System for monitoring remote servers based on instant messenger and method thereof
US8171474B2 (en) 2004-10-01 2012-05-01 Serguei Mankovski System and method for managing, scheduling, controlling and monitoring execution of jobs by a job scheduler utilizing a publish/subscription interface
CN101044463B (en) * 2004-10-20 2010-08-18 意大利电信股份公司 Method and system for monitoring performance of a client-server architecture
US7590508B1 (en) * 2004-10-22 2009-09-15 Sprint Communications Company L.P. Method and system for forecasting usage costs and computer capacity
KR20060084040A (en) * 2005-01-17 2006-07-21 삼성전자주식회사 Apparatus and method for dynamic qos management
US7546368B2 (en) * 2005-06-01 2009-06-09 Neustar, Inc. Systems and methods for isolating local performance variation in website monitoring
EP1739557A1 (en) * 2005-06-30 2007-01-03 Nortel Networks Limited Method for analyzing browsing and device for implementing the method
US20070019568A1 (en) * 2005-07-22 2007-01-25 Sbc Knowledge Ventures, L.P. Method of monitoring network elements supporting virtual private networks
US8130759B2 (en) 2005-07-29 2012-03-06 Opnet Technologies, Inc. Routing validation
US8140665B2 (en) * 2005-08-19 2012-03-20 Opnet Technologies, Inc. Managing captured network traffic data
US7623463B2 (en) * 2005-09-09 2009-11-24 International Business Machines Corporation Performance evaluation of a network-based application
GB2431315A (en) * 2005-10-11 2007-04-18 Agilent Technologies Inc Testing a telecommunications network
US8171174B2 (en) 2006-01-19 2012-05-01 Dell Products L.P. Out-of-band characterization of server utilization via remote access card virtual media for auto-enterprise scaling
US8078971B2 (en) * 2006-01-24 2011-12-13 Oracle International Corporation System and method for scripting explorer for server configuration
US8676958B1 (en) 2006-02-10 2014-03-18 Open Invention Network, Llc System and method for monitoring the status of multiple servers on a network
US7476013B2 (en) * 2006-03-31 2009-01-13 Federal Signal Corporation Light bar and method for making
US7746794B2 (en) * 2006-02-22 2010-06-29 Federal Signal Corporation Integrated municipal management console
US9346397B2 (en) 2006-02-22 2016-05-24 Federal Signal Corporation Self-powered light bar
US9002313B2 (en) * 2006-02-22 2015-04-07 Federal Signal Corporation Fully integrated light bar
US7810156B2 (en) * 2006-04-20 2010-10-05 Agiliance Inc. Automated evidence gathering
US8656006B2 (en) * 2006-05-11 2014-02-18 Ca, Inc. Integrating traffic monitoring data and application runtime data
US7805510B2 (en) * 2006-05-11 2010-09-28 Computer Associates Think, Inc. Hierarchy for characterizing interactions with an application
US8051163B2 (en) 2006-05-11 2011-11-01 Computer Associates Think, Inc. Synthetic transactions based on system history and load
US7814191B2 (en) * 2006-05-26 2010-10-12 The Pnc Financial Services Group, Inc. Methods and systems for network management using periodic status messages
US7761550B2 (en) * 2006-05-26 2010-07-20 The Pnc Financial Services Group, Inc. Network management for a plurality of agents using periodic status messages
JP4896593B2 (en) * 2006-06-05 2012-03-14 株式会社日立製作所 Performance monitoring method, computer and computer system
US20080004720A1 (en) * 2006-06-29 2008-01-03 Mckinney Howard M System and method for determining unimportant probe locations by examination of byte code by identifying trivial methods
EP1885083A1 (en) * 2006-08-03 2008-02-06 Acterna, LLC Triple play services tester
US8135990B2 (en) 2006-08-11 2012-03-13 Opnet Technologies, Inc. Multi-variate network survivability analysis
US8090766B2 (en) * 2006-08-15 2012-01-03 Microsoft Corporation System and method to identify, rank, and audit network provided configurables
US7979320B2 (en) * 2006-08-15 2011-07-12 Microsoft Corporation Automated acquisition and configuration of goods and services via a network
US8055747B2 (en) * 2006-08-15 2011-11-08 Microsoft Corporation Message based network transmission for selection and auditing of internet services
US20080148242A1 (en) * 2006-12-18 2008-06-19 Computer Associates Think, Inc. Optimizing an interaction model for an application
US9009680B2 (en) * 2006-11-30 2015-04-14 Ca, Inc. Selecting instrumentation points for an application
WO2008077111A1 (en) * 2006-12-19 2008-06-26 Gallup, Inc. A state discovery automation for dynamic web applications
US8429185B2 (en) 2007-02-12 2013-04-23 Microsoft Corporation Using structured data for online research
US7917507B2 (en) * 2007-02-12 2011-03-29 Microsoft Corporation Web data usage platform
US7779127B2 (en) * 2007-03-09 2010-08-17 Hewlett-Packard Development Company, L.P. System and method for determining a subset of transactions of a computing system for use in determing resource costs
US8095649B2 (en) 2007-05-09 2012-01-10 Opnet Technologies, Inc. Network delay analysis including parallel delay effects
US8892718B2 (en) * 2007-06-28 2014-11-18 Neustar, Inc. Monitoring web service transactions
US8095650B1 (en) 2007-07-30 2012-01-10 Compuware Corporation Methods and apparatus for real user monitoring including flash monitoring
ATE527835T1 (en) * 2007-10-18 2011-10-15 Ericsson Telefon Ab L M METHOD AND ARRANGEMENTS IN A MOBILE TELECOMMUNICATIONS NETWORK
US20090112809A1 (en) * 2007-10-24 2009-04-30 Caterpillar Inc. Systems and methods for monitoring health of computing systems
BRPI0722176A2 (en) * 2007-10-26 2014-04-08 Ericsson Telefon Ab L M METHOD FOR USE ON A PROXY MOBILE IP NETWORK, LOCAL MOBILITY ANCHOR Node, AND, MOBILE ACCESS CONNECTION POINT
US8326970B2 (en) * 2007-11-05 2012-12-04 Hewlett-Packard Development Company, L.P. System and method for modeling a session-based system with a transaction-based analytic model
US9021505B2 (en) * 2007-12-07 2015-04-28 Ca, Inc. Monitoring multi-platform transactions
US8645570B2 (en) * 2007-12-20 2014-02-04 Fast Health Corporation System and method for the issuance of an emergency text alert in response to the redirection of a website
US8214524B2 (en) * 2007-12-21 2012-07-03 Hostway Corporation System and method for selecting an optimal authoritative name server
US9021082B2 (en) * 2008-01-30 2015-04-28 Case Western Reserve University Internet measurement system application programming interface
US7831695B1 (en) * 2008-02-18 2010-11-09 Sprint Communications Company L.P. System and method for it system migration management
CA2669464C (en) * 2008-04-14 2020-03-31 Evertz Microsystems Ltd. Method and system for monitoring and controlling a video signal network
JP5253949B2 (en) * 2008-09-26 2013-07-31 ブラザー工業株式会社 Communication device and communication program
US8645922B2 (en) * 2008-11-25 2014-02-04 Sap Ag System and method of implementing a concurrency profiler
US8326973B2 (en) * 2008-12-23 2012-12-04 Novell, Inc. Techniques for gauging performance of services
US8266477B2 (en) 2009-01-09 2012-09-11 Ca, Inc. System and method for modifying execution of scripts for a job scheduler using deontic logic
US8635694B2 (en) * 2009-01-10 2014-01-21 Kaspersky Lab Zao Systems and methods for malware classification
US8028205B2 (en) * 2009-03-30 2011-09-27 Hartford Fire Insurance Company System for providing performance testing information to users
US8615739B2 (en) * 2009-04-23 2013-12-24 Hewlett-Packard Development Company, L.P. Resource monitoring
US8032791B2 (en) * 2009-07-07 2011-10-04 International Business Machines Corporation Diagnosis of and response to failure at reset in a data processing system
US8738710B1 (en) * 2009-08-05 2014-05-27 Nextel Communications Inc. Systems and methods of providing push-to-application services
US8666996B2 (en) * 2009-12-23 2014-03-04 Mastercard International Incorporated Methods and systems for detecting broken links within a file
JP5458308B2 (en) * 2010-06-11 2014-04-02 株式会社日立製作所 Virtual computer system, virtual computer system monitoring method, and network device
US9274842B2 (en) 2010-06-29 2016-03-01 Microsoft Technology Licensing, Llc Flexible and safe monitoring of computers
US20130083664A1 (en) * 2010-09-13 2013-04-04 Jeffrey T. Harris Remote management hardware platform for site monitoring with smart block i/o device
US8543868B2 (en) 2010-12-21 2013-09-24 Guest Tek Interactive Entertainment Ltd. Distributed computing system that monitors client device request time and server servicing time in order to detect performance problems and automatically issue alerts
US9009185B2 (en) * 2010-12-28 2015-04-14 Sevone, Inc. Scalable performance management system
US8677324B2 (en) * 2011-01-31 2014-03-18 Hewlett-Packard Development Company, L.P. Evaluating performance of an application using event-driven transactions
US8707111B2 (en) * 2011-02-09 2014-04-22 Ebay Inc. High-volume distributed script error handling
US9641247B2 (en) * 2011-05-03 2017-05-02 Monolith Technology Holdings, Llc System and method for monitoring unknown resources
US8671108B2 (en) 2011-09-02 2014-03-11 Mastercard International Incorporated Methods and systems for detecting website orphan content
US9679296B2 (en) 2011-11-30 2017-06-13 Retailmenot, Inc. Promotion code validation apparatus and method
US8725741B2 (en) 2011-12-04 2014-05-13 Riverbed Technology, Inc. Assessing application performance with an operational index
US20130305222A1 (en) * 2012-05-11 2013-11-14 Microsoft Corporation Development System
US9104630B1 (en) * 2012-10-24 2015-08-11 Google Inc. Online account reset, rollback, and backup
US9621480B2 (en) 2013-03-04 2017-04-11 Vigo Software Ltd Data acquisition pertaining to connectivity of client applications of a service provider network
US9767668B2 (en) * 2013-03-14 2017-09-19 International Business Machines Corporation Automatic adjustment of metric alert trigger thresholds
US10592915B2 (en) 2013-03-15 2020-03-17 Retailmenot, Inc. Matching a coupon to a specific product
US9563907B2 (en) 2013-06-13 2017-02-07 Vigo Software Ltd Offer based provision of fee based network access
US9423921B2 (en) * 2013-06-26 2016-08-23 Nicolas Bissantz System for providing information to a user
US9111037B1 (en) 2013-08-21 2015-08-18 Ca, Inc. Method and apparatus to enable mainframe computer testing for software testing management platform
US10037554B2 (en) 2013-10-30 2018-07-31 Vigo Software Ltd Aggregated billing for application-based network access and content consumption
EP3063650A4 (en) * 2013-10-30 2017-05-31 Hewlett-Packard Enterprise Development LP Recording an application test
US9753743B2 (en) 2013-12-05 2017-09-05 Entit Software Llc Identifying a common action flow
US9300679B1 (en) 2013-12-16 2016-03-29 8X8, Inc. System and method for monitoring computing servers for possible unauthorized access
US9306985B1 (en) 2014-03-25 2016-04-05 8X8, Inc. User configurable data storage
US9628436B1 (en) 2014-04-04 2017-04-18 8X8, Inc. User-configurable dynamic DNS mapping for virtual services
US11777814B1 (en) 2014-04-04 2023-10-03 8X8, Inc. User-configurable alerts for computing servers
US10355943B1 (en) 2014-04-04 2019-07-16 8X8, Inc. Apparatus and methods of analyzing status of computing servers
US10530935B1 (en) 2014-04-04 2020-01-07 8×8, Inc. Support services for virtual data centers
US10862948B1 (en) 2014-04-04 2020-12-08 8X8, Inc. Virtual data centers
TWI552002B (en) * 2014-04-22 2016-10-01 財團法人工業技術研究院 Method and system for dynamic instance deployment of public cloud
US10397407B1 (en) 2014-04-24 2019-08-27 8X8, Inc. Apparatus and method for user configuration and reporting of virtual services
US9189377B1 (en) * 2014-06-02 2015-11-17 Bank Of America Corporation Automation testing using descriptive maps
CN105335142B (en) * 2014-07-29 2019-03-15 国际商业机器公司 The method and apparatus of the performance bottleneck of Identifying transactions in transacter
US9558093B2 (en) * 2014-07-30 2017-01-31 Microsoft Technology Licensing, Llc Visual tools for failure analysis in distributed systems
US11195162B2 (en) * 2014-10-06 2021-12-07 Vmware, Inc. System for defining and tracking transactions of mobile devices
US10002365B2 (en) 2014-10-31 2018-06-19 The Nielsen Company (Us), Llc Methods and apparatus to identify publisher advertising behavior
US10355964B2 (en) 2014-10-31 2019-07-16 At&T Intellectual Property I, L.P. Method and system to capture selected network data
US11283697B1 (en) 2015-03-24 2022-03-22 Vmware, Inc. Scalable real time metrics management
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
US9910756B2 (en) * 2015-09-03 2018-03-06 International Business Machines Corporation Response-time baselining and performance testing capability within a software product
US9955021B1 (en) 2015-09-18 2018-04-24 8X8, Inc. Analysis of call metrics for call direction
US10044577B2 (en) * 2015-11-04 2018-08-07 International Business Machines Corporation Visualization of cyclical patterns in metric data
US10419310B1 (en) 2015-12-17 2019-09-17 8×8, Inc. Monitor device for use with endpoint devices
US9697110B1 (en) 2015-12-28 2017-07-04 Bank Of America Corporation Codeless system and tool for testing applications
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
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
US10379930B2 (en) * 2016-09-30 2019-08-13 Brother Kogyo Kabushiki Kaisha Non-transitory computer-readable medium storing computer-readable instructions for terminal device
US10860703B1 (en) * 2017-08-17 2020-12-08 Walgreen Co. Online authentication and security management using device-based identification
US11729043B2 (en) * 2017-10-06 2023-08-15 Cisco Technology, Inc. Traffic outage detection in the internet
US10999168B1 (en) 2018-05-30 2021-05-04 Vmware, Inc. User defined custom metrics
US11044180B2 (en) 2018-10-26 2021-06-22 Vmware, Inc. Collecting samples hierarchically in a datacenter
US11582120B2 (en) 2019-05-30 2023-02-14 Vmware, Inc. Partitioning health monitoring in a global server load balancing system
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
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
CN111176930B (en) * 2019-12-10 2023-02-07 未鲲(上海)科技服务有限公司 Component operation data processing method and device, computer equipment and storage medium
US11483227B2 (en) 2020-10-13 2022-10-25 Keysight Technologies, Inc. Methods, systems and computer readable media for active queue management
US11494292B2 (en) * 2021-02-26 2022-11-08 T-Mobile Usa, Inc. Log-based automation testing
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
CN115994076B (en) * 2023-03-23 2023-07-18 广州软件应用技术研究院 Self-checking method, system and platform for applying performance testing tool to loading machine

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5577197A (en) * 1992-10-29 1996-11-19 Mci Communications Corporation Test system for testing electronic transaction processing services at a common carrier network switch
GB2307318A (en) * 1995-11-14 1997-05-21 Mitsubishi Electric Corp Testing a networked system of servers
US5684945A (en) * 1992-10-23 1997-11-04 International Business Machines Corporation System and method for maintaining performance data in a data processing system
WO2000019320A1 (en) * 1998-09-30 2000-04-06 Netscout Service Level Corporation Evaluating computer resources by end-user emulation

Family Cites Families (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5864659A (en) * 1995-03-07 1999-01-26 Intel Corporation Computer server with improved reliability, availability and serviceability
EP0830611A4 (en) 1995-06-02 2007-05-09 Cisco Systems Inc Remote monitoring of computer programs
US5819066A (en) 1996-02-28 1998-10-06 Electronic Data Systems Corporation Application and method for benchmarking a database server
US5812780A (en) 1996-05-24 1998-09-22 Microsoft Corporation Method, system, and product for assessing a server application performance
US5696701A (en) * 1996-07-12 1997-12-09 Electronic Data Systems Corporation Method and system for monitoring the performance of computers in computer networks using modular extensions
US5938729A (en) 1996-07-12 1999-08-17 Microsoft Corporation System and method for monitoring server performance at a client computer
US5781703A (en) 1996-09-06 1998-07-14 Candle Distributed Solutions, Inc. Intelligent remote agent for computer performance monitoring
US5870559A (en) 1996-10-15 1999-02-09 Mercury Interactive Software system and associated methods for facilitating the analysis and management of web sites
US5732218A (en) * 1997-01-02 1998-03-24 Lucent Technologies Inc. Management-data-gathering system for gathering on clients and servers data regarding interactions between the servers, the clients, and users of the clients during real use of a network of clients and servers
US5787254A (en) 1997-03-14 1998-07-28 International Business Machines Corporation Web browser method and system for display and management of server latency
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
US6006260A (en) 1997-06-03 1999-12-21 Keynote Systems, Inc. Method and apparatus for evalutating service to a user over the internet
US5963963A (en) * 1997-07-11 1999-10-05 International Business Machines Corporation Parallel file system and buffer management arbitration
US5905868A (en) 1997-07-22 1999-05-18 Ncr Corporation Client/server distribution of performance monitoring data
WO1999006935A1 (en) * 1997-08-01 1999-02-11 Monks Robert A G Entreprise simulation module
US6324492B1 (en) * 1998-01-20 2001-11-27 Microsoft Corporation Server stress testing using multiple concurrent client simulation
US6205413B1 (en) 1998-06-11 2001-03-20 Chatschik Bisdikian End-user oriented performance monitoring system for interactive end-to-end data communications
US6189142B1 (en) * 1998-09-16 2001-02-13 International Business Machines Corporation Visual program runtime performance analysis
US6138157A (en) 1998-10-12 2000-10-24 Freshwater Software, Inc. Method and apparatus for testing web sites
US6243105B1 (en) 1998-11-19 2001-06-05 Ncr Corporation Drill-down method to historical data in a performance monitor using a platform independent program
US6446028B1 (en) * 1998-11-25 2002-09-03 Keynote Systems, Inc. Method and apparatus for measuring the performance of a network based application program
US6449739B1 (en) 1999-09-01 2002-09-10 Mercury Interactive Corporation Post-deployment monitoring of server performance

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5684945A (en) * 1992-10-23 1997-11-04 International Business Machines Corporation System and method for maintaining performance data in a data processing system
US5577197A (en) * 1992-10-29 1996-11-19 Mci Communications Corporation Test system for testing electronic transaction processing services at a common carrier network switch
GB2307318A (en) * 1995-11-14 1997-05-21 Mitsubishi Electric Corp Testing a networked system of servers
WO2000019320A1 (en) * 1998-09-30 2000-04-06 Netscout Service Level Corporation Evaluating computer resources by end-user emulation

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
"METHOD FOR PERFORMING AUTOMATED PSEUDO VIDEO RECORDING OF REMOTE COMPUTER SYSTEMS" IBM TECHNICAL DISCLOSURE BULLETIN,US,IBM CORP. NEW YORK, vol. 37, no. 4A, 1 April 1994 (1994-04-01), page 495 XP000446751 ISSN: 0018-8689 *
C. NOLAN: "A Look at e-Test Suite 3.1 by RSW" SOFTWARE TESTING & QUALITY ENGINEERING, [Online] July 1999 (1999-07), pages 60-61, XP002155308 Retrieved from the Internet: <URL:http://www.rswsoftware.com/news/artic les/ja99.pdf> [retrieved on 2000-11-28] *
LARSEN A K: "ALL EYES ON IP TRAFFIC. NEW APPS CAN MONITOR INTERNET AND INTRANET TRADDIC, BUT DO THEY DELIVER ENOUGH DATA TO HOLD ISPS TO THEIR PROMISES?" DATA COMMUNICATIONS,US,MCGRAW HILL. NEW YORK, vol. 26, no. 4, 21 March 1997 (1997-03-21), pages 54,56-60,62, XP000659549 ISSN: 0363-6399 *

Cited By (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1386240A2 (en) * 2001-03-30 2004-02-04 BMC Software, Inc. Synthetic transaction monitor
US7966398B2 (en) 2001-03-30 2011-06-21 Bmc Software, Inc. Synthetic transaction monitor with replay capability
US7792948B2 (en) 2001-03-30 2010-09-07 Bmc Software, Inc. Method and system for collecting, aggregating and viewing performance data on a site-wide basis
EP1386240A4 (en) * 2001-03-30 2008-06-04 Bmc Software Inc Synthetic transaction monitor
WO2002079909A2 (en) 2001-03-30 2002-10-10 Bmc Software, Inc. Synthetic transaction monitor
US7506047B2 (en) 2001-03-30 2009-03-17 Bmc Software, Inc. Synthetic transaction monitor with replay capability
US7461369B2 (en) 2001-03-30 2008-12-02 Bmc Software, Inc. Java application response time analyzer
EP1384153A2 (en) * 2001-05-04 2004-01-28 Netqos, Inc. Server-site response time computation for arbitrary applications
EP1384153A4 (en) * 2001-05-04 2005-08-03 Netqos Inc Server-site response time computation for arbitrary applications
WO2003005202A1 (en) 2001-07-06 2003-01-16 Computer Associates Think, Inc. Method and system for providing a virtual user interface
EP1405190A1 (en) * 2001-07-06 2004-04-07 Computer Associates Think, Inc. Method and system for providing a virtual user interface
EP1405190A4 (en) * 2001-07-06 2007-10-24 Computer Ass Think Inc Method and system for providing a virtual user interface
JP2003030060A (en) * 2001-07-19 2003-01-31 Hitachi Electronics Service Co Ltd Performance monitoring service system for web server
WO2003023621A3 (en) * 2001-09-10 2004-02-19 Mercury Interactive Corp Network-based control center for conducting performance tests of server systems
WO2003023621A2 (en) * 2001-09-10 2003-03-20 Mercury Interactive Corporation Network-based control center for conducting performance tests of server systems
US6993748B2 (en) 2001-10-26 2006-01-31 Capital One Financial Corporation Systems and methods for table driven automation testing of software programs
WO2003038550A3 (en) * 2001-10-26 2004-12-02 Capital One Financial Corp Systems and methods for table driven automation testing of software programs
WO2003038550A2 (en) * 2001-10-26 2003-05-08 Capital One Financial Corporation Systems and methods for table driven automation testing of software programs
US7437450B1 (en) * 2001-11-30 2008-10-14 Cisco Technology Inc. End-to-end performance tool and method for monitoring electronic-commerce transactions
US7836176B2 (en) 2001-11-30 2010-11-16 Cisco Technology, Inc. End-to-end performance tool and method for monitoring electronic-commerce transactions
EP2198398A4 (en) * 2007-08-28 2017-08-30 Sugarcrm Inc. Crm system and method having drilldowns, acls, shared folders, a tracker and a module builder
EP2198398A1 (en) * 2007-08-28 2010-06-23 Sugarcrm Inc. Crm system and method having drilldowns, acls, shared folders, a tracker and a module builder
WO2009068642A1 (en) * 2007-11-30 2009-06-04 International Business Machines Corporation Method for using dynamically scheduled synthetic transactions to monitor performance and availability of e-business systems
US8326971B2 (en) 2007-11-30 2012-12-04 International Business Machines Corporation Method for using dynamically scheduled synthetic transactions to monitor performance and availability of E-business systems
US8756575B2 (en) 2011-05-17 2014-06-17 International Business Machines Corporation Installing and testing an application on a highly utilized computer platform
US8832661B2 (en) 2011-05-17 2014-09-09 International Business Machines Corporation Installing and testing an application on a highly utilized computer platform
GB2491015A (en) * 2011-05-17 2012-11-21 Ibm Installing and testing an application on a highly utilized computer platform
US10884892B2 (en) 2017-06-28 2021-01-05 Fujitsu Limited Non-transitory computer-readable storage medium, display control method and display control device for observing anomolies within data

Also Published As

Publication number Publication date
CA2380358A1 (en) 2001-03-08
EP1214657A2 (en) 2002-06-19
US20020184575A1 (en) 2002-12-05
WO2001016753A3 (en) 2001-11-29
JP2003508849A (en) 2003-03-04
US6564342B2 (en) 2003-05-13
US6449739B1 (en) 2002-09-10
AU7112300A (en) 2001-03-26
AU763468B2 (en) 2003-07-24

Similar Documents

Publication Publication Date Title
US6449739B1 (en) Post-deployment monitoring of server performance
US7197559B2 (en) Transaction breakdown feature to facilitate analysis of end user performance of a server system
US6738933B2 (en) Root cause analysis of server system performance degradations
US20020198985A1 (en) Post-deployment monitoring and analysis of server performance
JP3526416B2 (en) Method, apparatus and program storage for monitoring and recording information
US9727405B2 (en) Problem determination in distributed enterprise applications
US6505248B1 (en) Method and system for monitoring and dynamically reporting a status of a remote server
US6631411B1 (en) Apparatus and method for monitoring a chain of electronic transactions
US6175832B1 (en) Method, system and program product for establishing a data reporting and display communication over a network
US6895437B1 (en) System for monitoring browsing activity of a visitor and decrementing a reference count upon a web page change for automatic unloading a client program
US7877435B2 (en) Method and system for transaction pipeline decomposition
US20030053420A1 (en) Monitoring operation of and interaction with services provided over a network
US20080052141A1 (en) E-Business Operations Measurements Reporting
GB2357679A (en) Monitoring of services provided over a network with recording and redisplay of user interactions with a web page
WO2006012546A2 (en) Method and computer program for web site performance monitoring and testing by variable simultaneous angulation
WO1999046692A2 (en) Providing network services through a common interface
Pham Real user monitoring for internal web application
Thirukonda et al. WebSpy: an architecture for monitoring web server availability in a multi-platform environment
Hassell Monitoring SBS Server Health and Performance

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 CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI 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 PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA 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 ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
AK Designated states

Kind code of ref document: A3

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CR CU CZ CZ DE DE DK DK DM DZ EE EE ES FI 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 PL PT RO RU SD SE SG SI SK SK SL TJ TM TR TT TZ UA UG UZ VN YU ZA ZW

AL Designated countries for regional patents

Kind code of ref document: A3

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

WWE Wipo information: entry into national phase

Ref document number: 2380358

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 71123/00

Country of ref document: AU

ENP Entry into the national phase

Ref country code: JP

Ref document number: 2001 520640

Kind code of ref document: A

Format of ref document f/p: F

WWE Wipo information: entry into national phase

Ref document number: 2000959879

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2000959879

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

WWG Wipo information: grant in national office

Ref document number: 71123/00

Country of ref document: AU

WWW Wipo information: withdrawn in national office

Ref document number: 2000959879

Country of ref document: EP