Abstract: A dynamic hash partition management scheme includes associating first partitions of a database with a first partition number, and second partitions of the database with a second partition number, associating first partitions of a database with a first partition number defining a total number of first partitions, and second partitions of the database with a second partition number defining a total number of second partitions. The method further includes, after receiving a request to insert a record in the database, determining an active partition number, and determining the first partition number as an active partition number. The method further includes determining a record key for the record, generating a partition identifier defining a partition of the first partitions using the record key and the active partition number, and inserting the record in the partition defined by the partition identifier.

Abstract: A monitoring system receives information from agents that monitors (e.g., unprivileged) containers, or applications in containers, executing across hosts to generate aggregated state information on a per-host basis. The system receives state information for each container, boot identifiers associated with the hosts of the container, and container identifiers. State information includes data describing the state of a container, or an application executing in the container. The boot identifier includes an identifier for a boot session of the host. The container identifier uniquely identifies each container. The monitoring system compares boot identifiers to determine containers that are co-located. If containers share a boot identifier, the monitoring system determines that the containers are co-located on the host that generated the boot identifier.

Abstract: Nodes on a token ring are rebalanced from an initial condition to a condition in which the load is optimally distributed based on a specified level of balance. Nodes are treated as electrically charged particles for purposes of the simulation and are assigned simulation values based on proportions between the size of the cluster, the computing power of the nodes, and the specified level of balance. A simulation module performs the rebalancing simulation by assigning the specified values to the particles and outputting, for each corresponding node, a token indicating the particle's final position and the position of the node on the token ring. The tokens are input to a redistribution module, which rebalances the cluster based on the generated tokens.

Abstract: A monitoring system using agents to dynamically collect state information at controllable intensity levels from components of systems. The system receives state information collected by an agent at a particular intensity level, and processes the state information to determine an updated intensity level for collecting state information by the agent, or by some other agent. The state information may include data indicating the performance of one or more components, such as process response times or other metrics. The intensity level for collecting further state information can be increased when, among other things, previously collected state information indicates more detailed monitoring for the component is appropriate. The intensity level for collecting further state information can be decreased when, among other things, previously collected state information indicates continued expected behavior.

Abstract: By monitoring requests to and from components of an application, an application analysis engine generates an inter-component graph for an application that identifies how the various components in the application are connected. When a performance issue is detected in association with the application, a traversal module traverses the inter-component graph to determine the possible execution paths that may have been the cause of the detected issue. The traversal module transmits requests to the correlation module to compare the metrics time series of the different components in the execution path with the detected issue. The correlation module compares metrics time series with the issue metric to identify correlations between execution patterns. The results of the correlation may be presented in a report that visually identify the root cause of the detected issues.

Abstract: A system correlates items of customer feedback to anomalous events that gave rise to the items of customer feedback and stores the correlation information in one or more databases. The correlation information it then later used to determine the probable causes of items of customer feedback received at a later time.

Abstract: An application performance management system is provided, which is adapted to analyze the performance of one or more applications running on information technology (IT) infrastructure. The application performance management system includes a data collector, an anomaly detector, an anomaly correlator, an anomaly ranking unit, and a source problem detector. The data collector collects performance metrics for one or more applications running on the IT infrastructure. The anomaly detector analyzes the performance metrics and detects anomalies, which may include performance metrics whose values deviate from historic values with a deviation that exceeds a predefined threshold. The anomaly correlator detects dependencies between plural anomalies and generates anomaly clusters. Each anomaly cluster includes anomalies that are correlated through one or more of the dependencies. The anomaly ranking unit ranks anomalies within an anomaly cluster.

Abstract: A software circuit breaker observes an amount of free memory available in an application server and a duration of a garbage collection process performed by the application server. The application server executes an agent comprising a plurality of processes for monitoring performance of the application server. Based on the amount of free memory and duration of the garbage collection process, the circuit breaker anticipates a likely crash of the application server. In response to anticipating the likely crash, the circuit breaker disables one or more processes of the agent.

Abstract: A series of graphical user interfaces allows a user to define rules for parsing unstructured and structured log data and generate an aggregate rule to identify events across multiple lines of one or more log files. A first graphical user interface allows a user to select a line from a log file under analysis, search for matching lines in the log file, define rules for parsing the log file, and tokenize attributes of the selected lines. A second user interface allows the user to aggregate defined rules so that messages may be correlated to identify events that occur across multiple lines.

Abstract: A system performs discovery and instrumentation of processes of an application based on process performance. The system includes one or more processors configured to: determine a duration score for a process indicating a relationship between a duration time for the process and a transaction time for a transaction including the process; determine an instrumentation threshold value; determine whether the duration score satisfies the instrumentation threshold value; and in response to determining that the duration score satisfies the instrumentation threshold value, instrument a second process invoked by the process to receive a second duration time for the second process when execution of the second process is detected in a second transaction trace of a second transaction. In some embodiments, the system prunes instrumented processes that primarily invoke subprocesses, and are thus unimportant for performance monitoring.

Abstract: Evaluating application performance includes: obtaining a request, processing the request, including invoking a function that accesses an external resource, determining whether a response time associated with invoking the function exceeds a threshold, and in the event that the response time exceeds the threshold, capturing a runtime attribute associated with the function.

Abstract: A software circuit breaker observes an amount of free memory available in an application server and a duration of a garbage collection process performed by the application server. The application server executes an agent comprising a plurality of processes for monitoring performance of the application server. Based on the amount of free memory and duration of the garbage collection process, the circuit breaker anticipates a likely crash of the application server. In response to anticipating the likely crash, the circuit breaker disables one or more processes of the agent.