Abstract:
In one embodiment, a system for managing communication connections in a virtualization environment includes a plurality of host machines implementing a virtualization environment, wherein each of the host machines includes a hypervisor, at least one user virtual machine (user VM), and a distributed file server that includes file server virtual machines (FSVMs) and associated local storage devices. Each FSVM and associated local storage device are local to a corresponding one of the host machines, and the FSVMs conduct I/O transactions with their associated local storage devices based on I/O requests received from the user VMs. Each of the user VMs on each host machine sends each of its respective I/O requests to an FSVM that is selected by one or more of the FSVMs for each I/O request based on a lookup table that maps a storage item referenced by the I/O request to the selected one of the FSVMs.
Abstract:
In one embodiment, a system for managing a virtualization environment includes a plurality of host machines, wherein each of the host machines comprises a hypervisor and one or more user virtual machines (user VMs), and a virtual machine controller, one or more virtual disks comprising a plurality of storage devices, a virtualized file server (VFS) comprising a plurality of file server virtual machines (FSVMs), wherein each of the FSVMs is running on one of the host machines. The VFS may be configured to receive a request for storage system information from a user and generate and send a response to the request, wherein the response is customized according to configuration information of the VFS that is specific to the user. The storage system information requested may include a total size of storage available to the user, and the user may have an associated storage quota limit.
Abstract:
Systems, methods, and other embodiments associated with modifying applications and monitoring exceptions are described. In one embodiment, a computer implemented method searches an executable code for code representing a database procedure call within the executable code. At a location in the executable code prior to the database procedure call, exception capturing code is inserted into the executable code that is configured to cause information to be collected about an exception when the exception occurs during execution of the database procedure call. After the database procedure call, termination code is inserted in the executable code, wherein the termination code is configured to terminate the collection of the information caused by the exception capturing code.
Abstract:
Provided are methods and computer program products for generating a model of network application health. Methods may include receiving activity data that corresponds to activities of multiple applications that are operable to execute on at least one networked device, and combining the received activity data to remove redundant portions thereof and/or to reconcile inconsistencies therein. Based on the received activity data, ones of the multiple applications are identified, and relationships between the identified applications are determined. A model is generated including the identified applications and the relationships therebetween, and a representation of the model is displayed. Related computer program products are also provided.
Abstract:
Transaction data is be accessed that was generated during monitoring of a plurality of transactions involving a plurality of software components in a system. From the transaction data, a flow of a first one of the plurality of transactions is determined that describes participation of a first subset of the plurality of software components in the first transaction. A flow of a second one of the plurality of transactions is also be determined from the transaction data, the flow of the second transaction describing participation of a different, second subset of the plurality of software components in the second transaction. An overlap is determined between the first and second transactions, the overlap involving a particular one of the software components included in both the first and second subsets of software components.
Abstract:
Disclosed herein are system, method, and computer program product embodiments for utilizing a backup catalog to perform synchronized backup and recovery of heterogeneous database systems. An embodiment operates by performing a global data backup of a heterogeneous database system comprising a first database management system (DBMS) at a first server and a second DBMS at a second server and recording a global data backup entry identifying the global data backup into a backup catalog. Upon receiving log backup notifications regarding asynchronous log backups on the first server and the second server, log backup entries identifying the asynchronous log backups are recorded into the backup catalog. To successfully perform a point-in-time recovery, the embodiment operates by using the backup catalog to identify data and log backups required for the recovery of the first and second servers to a recovery timestamp associated with the point-in-time recovery.
Abstract:
A performance monitoring and management system is provided for monitoring both server side and network side performance parameters of individual distributed transactions. The system uses correlation data which is transferred over a computer network to identify corresponding sender/receiver parts of a distributed transaction. Both server side tracing data and correlation data is transferred to an external correlation and monitoring server that creates per transaction end-to-end tracing data. Network probes are installed in the network infrastructures which monitor network conditions, like e.g. data transferred. Those network probes are configured in a way to identify and extract the correlation data used by the monitoring system and to tag created network measurements with this correlation data. Those tagged network measurements are then used to augment the per transaction end-to-end tracing data with corresponding network measurements.
Abstract:
An application which utilizes a single thread is monitored and context for the individual requests and business transactions operating on that platform are provided. A wrapper is placed is around an object that calls a request. The wrapper renames a request object. Request objects are renamed with a unique name when they are called. When a call stack is sampled, the sampler will retrieve the unique name. Performance data associated with the unique name may be correlated to a business transaction and particular request as metrics are subsequently analyzed. For subsequent reporting, such as call graph reporting, the report or call graph will have requests in the context of a particular business transaction and a particular request instance. This provides more context in reporting of an business application request for frameworks that utilize as single request for multiple threads.
Abstract:
A data source is identified that includes transaction data describing a set of transactions involving a particular software component and each transaction in the set of transactions includes a request and a corresponding response to the request. In some aspects, a modification to the data source is detected and the service model is caused to be generated based on detecting the modification. The service model is to model responses of the particular software component to requests in transactions based at least in part on the transaction data. A virtual service is caused to be generated based on the service model. The resulting virtual service can be configured to receive requests and generate virtual responses to the requests based on the service model to simulate responses of the particular software component.
Abstract:
The present technology correlates tasks between multiple threads of an application. A payload consisting of a task object may be identified as part of a method. Identification of the task object may be performed using instrumentation or some other method. Once the task object is identified, the payload may be instrumented to track the task object or payload and correlate the task object with other executing threads. Instrumenting the payload may include determining the constructor of the task object and instrumenting the task object constructors to determine what creates the task object. Once the source of a task object or payload is determined, the current thread having the task object as a parameter and another thread which creates the task may be tied together as part of a business transaction.