|
I have a lot of collected data, that change not smooth, but as a saw. So, if I set a trigger for this value, then the process of transition through this value could be the trigger to switch repeatedly, which naturally is very uncomfortable. Part of the problem can be solved by smoothing the curve by analysing the last N values??, but it does not always work, and increased reaction time.
It is possible to create a hysteresis in the trigger (this is described in the documentation), but it gives a very cumbersome and difficult to read formula like: (
{TRIGGER.VALUE} = 0 & {pbx: linkquality.rtc91.jitter.c ount (# 10,1, "gt" )}> 3) | ({TRIGGER.VALUE}
= 1 &
{pbx: linkq uality.rtc91.jitter.count (# 10,1, "gt")}
> 0). Also in this case, from the chart disappears the line that shows the threshold trigger.
It would be nice if in the triggers could be explicitly set two threshold switching back and forth, and that they both appeared on the charts.
|