For MySQL based systems, is there a way to force DM to update/refresh all 5 min avg trend data for all avg trending enabled data points, or for just elements of a particular protocol type, regardless of if a point’s value has changed or not? Similar to what happens when DM is restarted. Why do I ask? I would like to force DM once a day, say at midnight, to not only save avg trending data for values that have changed but also for values that have NOT changed. This way, there would always be at least one entry every day for every trended parameter. This would remove the need for special database cleaning logic to ensure data points whose values have not changed are still plotted without blank spots in the graphs. Thanks
Hi Jeff,
The closest thing to what you are asking is probably the following notify, which only works for history set parameters: NT_CLOSE_HISTORY_TREND_WINDOW (374) | DataMiner Docs
To my knowledge, even if trend windows are closed, there won’t be an additional entry in the database if the value is the same as previous windows. And there likely isn’t any integrated functionality to do this.
Thanks Floris. Hoping maybe someone else has an idea. It would be interesting to know how DM handles this in Cassandra based systems since Cassandra will simply delete records based on the record’s TTL without any concern whether the value has not changed in an extended period of time. Thanks again.