Custom counters can be used to indicate the performance, accuracy, or availability of a system. By default, they values of a custom timer are only displayed in reports and do not influence health rate. If a custom counter measure is to influence the performance data, it must begin with the prefix Pe_. In such cases, boundaries should indicate whether large values are considered good or bad. Example: MeasureSetBound("Pe_CPU", MEASURE_COUNTER_CUSTOMCOUNTER, 1, float(nBoundCpu1)); MeasureSetBound("Pe_CPU", MEASURE_COUNTER_CUSTOMCOUNTER, 2, float(nBoundCpu2)); MeasureIncFloat("Pe_CPU", fValue, "%"); For custom counters to influence accuracy , the prefix Ac_ is used. The prefix Av_ creates a custom counter that influences the availability rate. When such a counter is set, the monitor reports a problem in the accuracy or availability of the monitored site. Example: MeasureInc ("Av_Host Unavailable"); For monitors created by SilkPerformer Performance Explorer this prefix can be changed in the boundary editor. In summary, the following prefixes can be used with custom counters: Pe_ influences Performance Ac_ influences Accuracy Av_ influences Availability Old KB# 23945
↧