IBM Tivoli Composite Application Manager for Application Diagnostics, Version 7.1.0.1

Set alert actions and data actions


Regardless of the trap type, specify trap actions as part of the trap definition.

Trap actions include alerts and data actions. Alerts include messages sent by e-mail or SNMP, whereas data actions capture Method Traces, Stack Traces or Thread Dumps.

Trap actions occur when a trap triggers. You can configure alert actions to be suppressed, to avoid getting spammed by alerts.


Set alert actions and data actions:

  1. You can set trap alerts on the Step 3 - Set Trap Alerts page, which is part of the trap creation process. To arrive at this page, see Set an Application trap or Set a Server Resource trap.

  2. For the Trap Alert settings, in the condition field, enter the number of times the trap will trigger before the action is taken.

    This value will be applied to all the trap actions defined in the next two steps. To define multiple actions, each with a different condition, repeat steps 2-4 once for each distinct condition.

  3. 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, the three severity levels of the application monitor are mapped to the warning levels of Tivoli listed in the following table:

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

  4. Add at least one action, either an alert action (e-mail or SNMP message) or a data action (Method Trace, Stack Trace or Thread Dump.) (The Thread Dump is not available on the Windows platform.)

  5. To select an action, click its check box. For the e-mail action, also enter the list of e-mail addresses to which the message will be sent.

  6. Click Add to add the actions to your trap. Repeat this step until you have added all the actions you want. You can change the values of the condition and severity fields (steps 2 and 3) each time you add a new action. If you select Component/Method Trace as the Data Action for an In-flight-based trap, the method trace may contain a "-1" for Depth on some events in the method trace. In-flight transactions, by definition, are incomplete transactions, so the request stacks of those transactions will be incomplete.

  7. Set the Default Suppression setting if you want to avoid getting spammed by Alert Actions that might occur close together in time.

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

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

  10. Click either Save or Save & Activate. If you click Save, the Trap and Alert Management page opens displaying your new trap. If you click Save & Activate, the Activate page opens. To activate a trap, see "Activating a Trap".


Results

You can configure the Time Interval in the Trap Alert Settings page to milliseconds, seconds, minutes, hours, days or weeks. The smallest available time interval unit is milliseconds, certain trap types might not be able to use milliseconds as the time unit. Use the following table as a guideline for setting the Time Interval value with default Managing Server and data collector settings.

Trap Type Target Type Minimum Time Interval
Server Resource Trap Average Platform CPU % Usage 5 (min)
Average JVM CPU % Usage 5 (min)
JVM Heap Size 1 (min)
Average JVM Heap Size after GC 1 (min)
Request Frequency 1 (min)
Number of Sessions 1 (min)
Application Trap Occurrence 1 (ms)
CPU Time 1 (ms)
Wait Time 1 (ms)
Resident Time – In-Flight 1 (ms)
Resident Time – Complete 1 (ms)
Resident Time – Misbehaving Transaction 1 (ms)
Uncaught Exceptions 1 (ms)
Lock Acquisition Time – In-Flight 1 (ms)
Lock Acquisition Time – Completed 1 (ms)


Parent topic:

Trap and alert management


Related topics

Activate a trap