Ca, Inc.

Nice Systems Technologies Inc.

David Brooke Martin

Mark Jacob Addleman

Marco Gagliardi

Erhan Giral

Andreas Gerhard Reiss

Corey Cohen

Michael Steven Walker

Arkadiy Isaakovich Reznik

For each event detected during execution of a monitored application comprising a plurality of application components, a determination is made of which of the plurality of application components corresponds to the detected event. Also, a dependency subgroup that includes the application component that corresponds to the detected event is identified, wherein a dependency subgroup indicates dependencies among a subgroup of the plurality of application components. A location within the dependency subgroup of the application component corresponding to the detected event is determined. An order of correction for the application components determined to correspond to detected events are determined based, at least in part, on the determined location. Correction of the application components determined to correspond to detected events are initiated according to the determined order of correction.

Ordered correction of application based on dependency topology

A two-pass technique for instrumenting an application is disclosed. One pass may be performed statically by analyzing the application and inserting probes while the application is not running. Another pass may be performed dynamically by analyzing data collected by the probes while the application runs to derive metrics for the probes. One or more metrics for each probe may be analyzed to determine whether to dynamically modify the probe. By dynamically modifying the probe, the application does not need to be shut down. Dynamically modifying the probe could include removing the probe from the application or moving the probe to another component (e.g., method) in the application, as examples. For example, the probe might be moved to a component that is either up or down the call graph from the component that the probe is presently in.

Two pass automated application instrumentation

A business rules engine includes dynamic objects to support dynamically addressable facts. The business rules engine is configured to reduce the need for developer resources to provision resources and adjust/adapt input data and output which would traditionally be required. As a result significant cost advantages are provided in the use of a business rules engine.

Business rules engine with dynamically addressable facts

Growing community of inventors

San Jose, CA, United States of America

David Brooke Martin