IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Set a Server Resource trap


A Server Resource trap measures a variety of target types.

The system will trigger a trap after exceeding the threshold for the metric you set.  When the system meets the definition of the trap an alert occurs. For example, set a trap to alert you when a server is unavailable 2 times, and after a server is unavailable you can select to receive an e-mail.   


Set a Server Resource trap:

  1. From the top navigation, click...

      Problem Determination > Trap & Alert Management > Create Trap > Server Resource trap

  2. Select one of the following target types from the list box.

    • CPU

        Average Platform CPU % Usage

        Based on the average platform CPU usage over five minutes, the Publish Server retrieves CPU usage at regular intervals (60 seconds by default) and calculates the average platform CPU over five minutes.

      • Average JVM CPU % Usage

        Based on the average JVM CPU usage over five minutes, the Publish Server retrieves CPU usage at regular intervals (60 seconds by default) and calculates the average JVM CPU over five minutes.

    • Memory

      • JVM Heap Size

        Based on the JVM Heap Size of the data collector, the Publish Server retrieves JVM Heap Size from the data collector at regular intervals (60 seconds by default) and checks the heap size from that measure.

      • Garbage Collection Frequency

        Garbage Collection is calculated over one minute.

      • Average JVM Heap Size after Garbage Collection

        The trap triggers when the average JVM Heap size exceeds the size configured in the trap

    • Application Capacity

      • Number of Sessions

        Based on the number of user sessions that are currently in use by the application server.

      • Average Response Time

        Publish Server triggers the trap if the average response time exceeds the time configured in the trap condition.

      • Server available

        Publish server triggers the trap when the Server (data collector) becomes available.

      • Server unavailable

        The Publish server triggers the trap if the Server (data collector) goes down or becomes unavailable.

      • Uncaught Java Exceptions

        Based on the rate of the Java exceptions that occur in applications and includes data about the failure. It is calculated over 60 seconds. Publish server triggers the trap if the Servlet error rates exceed the number configured in the trap condition.

      • Request Frequency

        Number of requests per minute.

    • Resource Pool

      • Thread Pool % Usage

        Publish Server triggers the trap if the Thread Pool % Usage of a particular server exceeds the threshold specified in the trap condition.

      • JCA Pool % Usage

        Publish Server triggers the trap if the JCA Pool % Usage of a particular server exceeds the threshold specified in the trap condition.

      • JDBC Pool % Usage

        Publish Server triggers the trap if the JDBC Pool % Usage of a particular server exceeds the threshold specified in the trap condition.

  3. Click Next. The Define Trap page opens.

  4. Enter a threshold that will send out an alert when it triggers the trap after meeting the condition.

  5. Click Next. The Set Trap Alerts page opens.

  6. For the Trap Alert settings, under Condition enter the number of times the trap occurs before the system takes an action. Specify the amount of time under Time Interval to monitor how many times the trap met its conditions.

  7. Click to select the serverity level from the list box.

    The application monitor has three severity levels. Since the application monitor provides SNMP integration with Tivoli, map the three severity levels of the application monitor to the warning levels of Tivoli listed in the following table:

    ITCAM severity level Tivoli warning level
    Low Harmless
    Medium Minor
    High Critical

  8. Select an action or multiple actions, such as sending an e-mail or SNMP message, for the system to take when the condition is met.

  9. The Data Action–Heap Dump is only available if you select JVM Heap Size or Average JVM Heap Size after Garbage Collection as your Target type.

  10. Click Add to add the alert to your trap.

  11. Set the Default Suppression settings by entering the amount of time you want to delay alerts after the first alert is sent.

  12. Click Next to proceed. The Name Trap page opens.

  13. Enter a name and descriptive text for your trap.

  14. Click either Save or Save & Activate.

  15. If you click Save, the Trap and Alert Management page opens displaying your new trap.

  16. If you click Save & Activate, the Activate page opens. To activate a trap, see Activating a Trap .


Results

If you select the <= operator while creating or modifying the Request Frequency target type, then the following sequence of events occurs:

  1. The trap action does not trigger if no transactions are received by the Publish Server after activating the trap.

  2. Trap threshold checking begins after the first transaction received by the Publish Server activates the trap.

When setting a trap, you can select multiple trigger conditions and alerts for each action set. Each trap is required to have at least one action but can have multiple actions set.


Parent topic:

Trap and alert management


Related topics


Activate a trap