Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: minor edits

...

The extensions are described and their source is available for free download at: at http://www.appdynamics.com/community/exchange/

...

Roll up Strategy

Description

AVERAGE

Average of all one-minute values when adding it to the 10-minute granularity table; the average of all 10-minute values when adding it to the 60-minute granularity table.

SUM

Sum of all one-minute values when adding it to the 10-minute granularity table; the sum of all 10-minute values when adding it to the 60-minute granularity table.

CURRENT

Last reported one-minute value in that 10-minute interval; the last reported ten-minute value in that 60-minute interval.

...

For example, if a tier has two nodes, Node A and Node B, and Node A has 3 errors per minute and Node B has 7 errors per minute, the INDIVIDUAL qualifier reports a value of 5 errors per minute and and COLLECTIVE qualifier reports 10 errors per minute. INDIVIDUAL is appropriate for metrics such as % CPU Busy where you want the value for each node. COLLECTIVE is appropriate for metrics such as Number of Calls where you want a value for the entire tier.

...

  1. Select the execution style from one of the following:

    Execution Style

    Description

    Example

    continuous

    Choose continuous if you want data collection averaged over time – for example, average CPU usage over a minute.
    For the monitor to be declared as 'continuous', the script should also run in an infinite loop. This ensures that the script keeps running until the Standalone Machine Agent process is terminated.

    while [ 1 ]; do
    ... the actual script goes here ...
    sleep 60
    done

    periodic

    Choose periodic to report data from system performance counters periodically. The periodic task runs every minute by default and the data is aggregated. 

    To specify a different frequency, use the execution-frequency-in-seconds element. The execution frequency must be less than 60. For periodic execution style, you can also specify the timeout setting as shown in the example.

    <monitor-run-task>

    ...

    <execution-style>periodic</execution-style> <execution-frequency-in-seconds>30</execution-frequency-in-seconds> <execution-timeout-in-secs>30</execution-timeout-in-secs>

    ...

    </monitor-run-task>

  2. Add the name of your script file to the <file> element  in  element in the monitor.xml file. Be sure to use the correct os-type attribute. The os-type value should match the value returned from calling System.getProperty("os.name")

    No Format
    <file os-type="your-os-type">{script file name}</file>

    You can use either the relative or absolute path of the script.

...