When sending a GetTrendDataMessage through SLNet to get the hourly average trending, I'm also requesting the iStatus.
In the past this contained value "-13" after an element restart to indicate when the first value entered.
Since the upgrade to DataMiner version 10.1.10.0-10897, I'm not seeing this iStatus value -13 anymore. It only contains -1 to indicate that the element is starting up, followed by the hourly "60" iStatus value.
I was wondering if this is intended behavior the "-13" is not present anymore or if there's a software issue since DataMiner 10.1.10.0?
I have a driver that is requesting the trending and is relying on this "-13" value to know when a valid value entered and it now seems to be pointing to the value before the upgrade to 10.1.10 as that was the last -13 that was written into the database even though there were element restarts in between.
As of RN26730 these points (together with -12 and -14) have been removed, as they were not used by the client at all, and were not always correctly saved to begin with. After consulting both client and system dev these points got removed during the trending rework.
But as -13 was supposed to be “first value received for the parameter in question since the element was started”, the point itself is superfluous as the “-1” point still exists, which indicates when an element is starting up. The first data point after a “-1” will thus be the same as the one which before had “-13”.