Hi everyone,
I am trying to configure relative alarms for Tx Bitrate parameter in one of my templates and have the baseline automatically updated. Now this works without issues, but somehow the trending (so far a few days have been recorded) is not recognized as the 'Trending' column is empty and it says "No average trending enabled...." when hovering the mouse over it, although it is very well enabled (see screenshots below). Therefore, the alarm does not work. Both alarm and trend template are assigned to the same element.
Alarm template:
Baseline config:
Trend template:
Element trending:
Perhaps I have missed something?
EDIT: Changed the alarm template picture for better readability.
BR,
Max
It's indeed a known issue if there are still not enough trend points stored in the database to recognize the parameter as being trended that it will not properly show up but on the other hand we had a recent similar case on 10.2.7 where we could not reproduce the "no trending available" anymore either after re-enabling the trend template. Could you confirm which version you were running your tests so i can chase this further as a potential issue?
Hello Marlies,
After checking my messages, our DMS was on 10.2.0.0-11517 at that time.
thanks for the feedback!
After another test, the message “No average trending enabled” no longer appeared immediately after enabling trending on the parameter and the baseline was calculated automatically. Also an alarm was generated, just as it should. Maybe the first test had a bad configuration start. Anyway I see this as resolved.