Hi Dojo,
I've been running a test with the smart baseline config, same option as shown in this post to detect continuos degradation (over 7 days): for some reason, though, even if the Delta was exceeded at a given time (simulated a drop to 0 for the bitrate), the root time of the alarm did not coincide with the bitrate drop to zero - it was some hours later: this is shown in the trends, as the minor violation (light blue) kicks in after - when our test feed dropped to zero we didn't have an alarm (the axis has still the green colour):
Wondering if this can be related to the "auto" option or if there is something else that I'm missing:
When leaving the "Auto" option checked, what root time is expected for the alarm?
Hi Alberto,
That behavior does seem to be unexpected. We took a look at this with a few colleagues but currently do not have an idea on what is causing this. Could you share the following?:
- Alarm template of this parameter
- Value of this parameter from the last 7 days. (A screenshot of the trend graph containing this period would be great)
We will have another look at it then. Thanks.
Marking this as solved, as the observed behaviour was due to misconfiguration in the test set-up
Thanks Thomas, adding screenshots – I think the issue was with the lower delta rather than the automatically updated baseline – I’ve realised when I got this feedback on a related post: https://community.dataminer.services/question/alarm-template-baseline-delta-range-vs-high-or-low/