×

Method and apparatus for exposing monitoring violations to the monitored application

  • US 7,631,073 B2
  • Filed: 01/27/2005
  • Issued: 12/08/2009
  • Est. Priority Date: 01/27/2005
  • Status: Expired due to Fees
First Claim
Patent Images

1. A method in a data processing system for exposing monitoring violations to a monitored application, the method comprising:

  • configuring, by a processor of an application server, a monitored application to interact with a monitoring application, wherein configuring a monitored application comprises;

    receiving, by the processor, a monitoring component from a user;

    inserting code into the monitored application using the monitoring component; and

    receiving, by a performance monitoring engine of the processor, at least one policy and at least one threshold defined by the user, wherein the at least one policy and the at least one threshold is associated with a transaction in the monitored application;

    initiating the transaction in the monitored application, wherein initiating the transaction comprises;

    generating the transaction using the code inserted into the monitored application using the monitoring component;

    matching the transaction against the at least one policy and determining if the at least one policy matches the transaction, wherein determining if the at least one policy matches the transaction comprises examining a policy mapper in a management agent to determine if the transaction is defined in the at least one policy;

    in response to determining that the at least one policy matches the transaction;

    returning a valid Application Response Measurement correlator; and

    invoking a start method on the performance monitoring engine using the valid Application Response Measurement correlator;

    the monitoring application querying the monitored application for a status of the transaction at the monitored application, wherein querying a status of the transaction comprises retrieving a status code from the performance monitoring engine;

    the monitored application determining whether the transaction is in a violation state based on the status at the monitored application, wherein the transaction is determined to be in a violation state if the status code is determined to be greater than zero, and wherein the transaction is determined to not be in a violation state if the status code is determined to be equal to zero;

    in response to determining that the status code is greater than zero such that the transaction is in a violation state, taking corrective actions to correct a violation, wherein taking corrective actions to correct a violation comprises;

    the monitored application alerting the monitoring application of the violation;

    the monitoring application aborting the transaction using the code inserted into the monitored application by the monitoring component, wherein the code invokes an abort method on the performance monitoring engine; and

    taking an alternative code path to correct the transaction; and

    in response to determining that the status code is not greater than zero;

    determining whether the status code is equal to zero; and

    in response to determining that the status code is equal to zero such that the transaction is not in a violation state, continuing with the transaction until the transaction is completed.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×