Abstract:
Wireless network performance test is initiated and test results are gathered from multiple independent wireless client devices which simplify and assist in the process of analysis and generation of test reports. The system for emulating multiple independent wireless client device in the cloud comprising a cloud platform (104) consisting a plurality of virtual machines (110a-110n); a plurality of USB wireless adapters (106); and a device agent (102). The method for emulating multiple independent wireless client devices in the cloud comprising steps of setting up test environment by user (202); reading files by Device Agent and providing list of USB devices in cloud platform which can be used (204); specifying number of wireless client to be created by user (206); launching different virtual machines in the cloud platform by the Device Agent by using virtual machine images provided by the user based on settings in the configuration files (208); mapping and attaching physical USB devices to virtual machines in the cloud platform to create multiple independent wireless client device by the Device Agent (210); injecting test automation scripts into all virtual machines by the Device Agent and initiating test execution in all virtual machine in the cloud platform based on settings in the configuration files (212); and gathering results from all virtual machines by the Device Agent upon completion of test execution based on the settings in the configuration files (214); and analyzing test results received from all virtual machines and generating test report (216).
Abstract:
A tracing system may define an origin for consolidating and comparing trace paths within a traced application. A tracer may define an identifier that may be passed through a tracing route, and the identifier may be defined to capture specific instances or groups of instances of traces. The traces may be consolidated into a graphical representation of the program flow. The identifier may be passed across various boundaries, including function boundaries, library boundaries, application boundaries, device boundaries. An analysis system may consolidate or aggregate trace results having the same identifier, and may render such data graphically or provide statistics using the identified datasets.
Abstract:
Diagnostic data is received at a multi-tenant data center. The diagnostic data is from a data system instance and the multi-tenant data center hosts data from a plurality of organizations. The diagnostic data is stored at the multi-tenant data center and a rules engine runs on the diagnostic data and provides optimization recommendations for the instance of the data system to which the diagnostic data was collected.
Abstract:
A technique for communicating with multiple Converged IT Infrastructures (CITIs) includes accessing any CITI that is part of a group of multiple CITIs by accessing a single CITI within the group. In an example, each CITI has a representative converged infrastructure coordinator (CIC), which stores information about the respective CITI. When any CITI in the group receives a request from a client for information about any other CITI in the group, the CIC of the CITI receiving the request contacts the CIC of the other CITI and obtains the requested information about the other CITI from its CIC. In some examples, the CIC also acts to aggregate, filter, and/or analyze information gathered from multiple CITIs in the group, and thus allows clients to receive processed data pertaining to many CITIs in response to simple commands. The technique includes accessing any CITI that is part of a group of multiple CITIs by accessing a single CITI within the group. In this manner, a client need only communicate with a single CITI to obtain information about any CITI in the group. The burdensome task of maintaining communication with multiple CITIs is therefore reduced or eliminated altogether. The CIC may also aggregate, filter, and/or analyze information gathered from multiple CITIs, thereby allowing clients to receive processed data pertaining to many CITIs in response to simple commands.
Abstract:
The present invention relates to a system and method for assessing application performance, in some embodiments, the analysis considers external factors, such as business hours, time zone, etc., to identify or recognize distinctive intervals of application performance. These distinctive intervals correspond to different periods of activity by an enterprise or business and may occur in a cyclical manner or other type of pattern. The distinctive intervals defined by external factors are employed in the analysis to improve aggregating of statistics, setting of thresholds for performance monitoring and alarms, correlating business and performance, and the modeling of application performance. The metrics measured can include, among other things, measures of CPU and memory utilization, disk transfer rates, network performance, queue depths and application module throughput. Key performance indicators, such as transaction rates and round-trip response times may also be monitored.
Abstract:
A method and system (20) is provided for condition based monitoring reliability maintenance capabilities for an asset (70), such as one or more machines, by establishing a network including of a sensor (60) or a plurality of sensors installed, temporarily or in generally fixed locations, on asset (70), wherein sensor (60) provides time sequenced operational, information in the form of data based on vibrations, temperature, electrical signals, or other operating conditions. Sensors (60) are connected to a local controller (40) which transmits the data via a local or wide area network (45), either through wired or wireless communication paths, in data packets, each, containing divided portions of the operational information. The data packets are mapped and stored, into multiple, dedicated databases for ease of retrieving and analyzing the data. Preferably, a cloud-based storage arrangement (120) is employed, to storing the mapped data.
Abstract:
Embodiments of the present invention include systems and methods for monitoring user activity. In embodiments, a front-end component collections data that may be useful to an administrator or others in determining or inferring what a user was doing or trying to do when interacting with an application, and the front-end component communicates at least some of this data to a back-end component. In embodiments, the communication of data related to the user activity is piggy-backed with typical transmissions, such as requests and responses, to reduce the overhead of the user activity monitoring.
Abstract:
The present invention relates to managing data generated by software transactions, such as event tracing software. In one embodiment, data generated by event tracing software is monitored. The throughput of the data generated may then be modulated based on various criteria, such as a target data rate. The throughput target may be specified on a per-system basis or individual basis. Based on the throughput, the level of detail recorded is modulated. Individual processes may determine a limit or quota depending on their contribution to the throughput. In one embodiment, the method calls for a trace are modified with different property specifications to meet a desired throughput of event tracing data.
Abstract:
A method of controlling webpage behaviour on a web enabled device 3 in order to assist in, for example, collection of monitoring information, preserving session context, and improving security. The method includes monitoring a user interaction with a webpage (step 203), using a client side module 31 at the web enabled device 3, and determining whether predetermined conditions are satisfied (step 204). Where the predetermined conditions are satisfied the further steps below are carried out: capturing details concerning an intended result of said user interaction (step 205), using the client side module; at least temporarily preventing occurrence of the intended result of said user interaction using the client side module (step 206); carrying out additional processing (step 207) using the client side module; determining a controlled result (step 208), using the client side module, in dependence on said intended result and the additional processing; and causing the controlled result to occur (step 209). The additional processing might, for example, include collecting monitoring information, dynamically re-writing the URL to allow preservation of session context, or performing in checks or modifications to improve security.