Abstract:
Business transactions and the nodes processing the transactions are monitored and actions are applied to one or more nodes when a performance issue is detected. A performance issue may relate to a metric associated with a transaction or node that processes the transaction. If a performance metric determined from data captured by monitoring does not satisfy a health rule, the policy determines which action should be performed to correct the performance of the node. When a problem is detected for multiple nodes, the present technology may address a subset of the multiple nodes rather than apply an action to each node experiencing the problem. When a solution is found to correct the problem with the subset of nodes, the solution may be applied to the other nodes experiencing the same problem.
Abstract:
A system and method for tracing individual transactions on method call granularity is disclosed. The system uses instrumentation based transaction tracing mechanisms to enhance thread call stack sampling mechanisms by a) only sampling threads executing monitored transactions while execution is ongoing b) tagging sampled call stacks with a transaction id for correlation of sampled call stacks with instrumentation bases tracing data. The combination of instrumentation based tracing with thread call stack sampling reduces sampling generated overhead by only sampling relevant thread, and reduces instrumentation generated overhead because it allows reducing instrumentation.
Abstract:
According to one aspect of the present disclosure, a system and technique for capacity forecasting is disclosed. The system includes a host having a processor unit and a memory. Resource data stored associated with an environment is stored in the memory, the resource data comprising inventory information of applications, processing resources and storage resources of the environment. A ledger module is executable by a processor unit to: create a capacity-associated transaction; identify and link at least one of an application, processing resource and storage resource to the transaction from the resource data; determine an initiation time and duration associated with the transaction; and forecast a change in capacity of at least one linked storage resource for the transaction and a time of the change in capacity.
Abstract:
Apparatus comprising logic analyser circuitry comprises a succession of two or more successive trigger condition detectors each configured to detect a match between a respective trigger condition and data handling activity relating to data handling transactions each having a respective transaction identifier; the succession of trigger condition detectors being configured so that a detection by a trigger condition detector of a match with its respective trigger condition enables a next trigger condition detector in the succession to initiate detection of a match with the respective trigger condition of that next trigger condition detector; and a transaction identifier detector associated with a first trigger condition detector in the succession, configured to detect the transaction identifier relating to a data handling transaction for which a match is detected by the first trigger condition detector, and to supply the detected transaction identifier to a subsequent trigger condition detector in the succession of trigger condition detectors; in which the subsequent trigger condition detector is configured to apply the detected transaction identifier as at least a part of its respective trigger condition so as to detect a match only in respect of a data handling transaction having that transaction identifier.
Abstract:
Methods, systems, and computer readable media for scaling a workload are disclosed. According to one exemplary method, the method occurs at a network equipment test device. The method includes generating a first workload comprising a plurality of messages associated with one or more transactions. The method also includes determining one or more workload segments in the first workload, wherein each of the one or more workload segments represents one or more messages associated with a particular transaction and generating a second workload using the one or more workload segments, wherein the second workload includes a number of the workload segments based on a workload scale attribute.
Abstract:
Systems and methods for performance and security management of the computing infrastructure that supports an application deployed in a hosted computing environment are described. In one embodiment, for example, a system comprises agents installed on hosts. The agents capture and record system events from operating systems on the hosts that result from application component processes executing on the hosts. The system further includes a collection and analysis engine that obtains captured and recorded system events from the agents, identifies captured and recorded system events that pertain to an application transaction, and produces, from the identified system events, metric data reflecting quantity of computing resources used by the application component processes to process the application transaction. The system also includes a web dashboard that presents the metric data to a user, for example, on a web page.
Abstract:
An exactly once semantics (EOS) system of a storage input/output (I/O) stack implements a technique ensuring that non-idempotent operations occur exactly once in a storage system embodied as a node of a cluster. Illustratively, a first layer of the storage I/O stack may act as a client issuing a non-idempotent operation to second layer of the stack, which may act as a server. According to the technique, the EOS system may wrap (i.e., encapsulate) the non-idempotent operation within a transaction embodied as an EOS transaction data structure having a transaction identifier that uniquely identifies the transaction. The server may complete the transaction and reply with a result to the client, which may acknowledge receipt of the reply. In response to a crash and subsequent recovery of the node, the EOS system may determine whether the transaction had completed prior to the crash. If so, the EOS system ensures that the transaction is not re-played (re-executed). Otherwise, the EOS system allows execution of the transaction such that the transaction occurs exactly once.
Abstract:
Aspects of the subject disclosure are directed towards monitoring application performance during actual use, particularly mobile application performance. Described is instrumenting mobile application binaries to automatically identify a critical path in user transactions, including across asynchronous-call boundaries. Trace data is logged by the instrumented application to capture UI manipulations, thread execution, asynchronous calls and callbacks, UI updates and/or thread synchronization. The trace data is analyzed to assist developers in improving application performance.
Abstract:
Embodiments of the invention relate to implementing run-time instrumentation indirect sampling by address. An aspect of the invention includes a method for implementing run-time instrumentation indirect sampling by address. The method includes reading sample-point addresses from a sample-point address array, and comparing, by a processor, the sample-point addresses to an address associated with an instruction from an instruction stream executing on the processor. The method further includes recognizing a sample point upon execution of the instruction associated with the address matching one of the sample-point addresses. Run-time instrumentation information is obtained from the sample point. The method also includes storing the run-time instrumentation information in a run-time instrumentation program buffer as a reporting group.
Abstract:
Embodiments of the present invention disclose a method for recovery of a two-phase commit transaction. A computer transmits a first transaction identifier to a data store, wherein the first transaction identifier defines a two-phase commit transaction. The computer transmits a prepare command for the first transaction identifier to a first resource manager. The computer determines if a failure and restart occurred within a distributed data processing environment, wherein the failure and restart occurs after the first resource manager receives an end command, but prior to completing execution of the prepare command for the first transaction identifier. Responsive to determining the failure and restart did occur within the distributed data processing environment, the computer retrieves the first transaction identifier from the data store. The computer transmits a rollback command for the retrieved first transaction identifier to the first resource manager.