Please Note This forum exists for community support for the Mango product family and the Radix IoT Platform. Although Radix IoT employees participate in this forum from time to time, there is no guarantee of a response to anything posted here, nor can Radix IoT, LLC guarantee the accuracy of any information expressed or conveyed. Specific project questions from customers with active support contracts are asked to send requests to support@radixiot.com.
Live Vaues not updating on ES watchlist
-
We have an ES that is streaming to a cloud server via persistent TCP.
Both are running v3.3.4
ES polls/updates every minute, and poll times are around 9 seconds.
ES logs on interval every 15 minutes.
Cloud server logs on interval every 5 minutes.
Here is the issue.. Cloud server keeps live values in the watchlist current to the last 5 minutes however the ES watchlist does not keep live values in its watchlist or even values up to the past 15 minutes although the ES point detail page will show values up to the past 15 minutes as the last 10 values in the history.
My question is why the ES watchlist will not reflect these latest values and instead reports that the point values may not be reliable? -
Could you post a screenshot of your /internal/queueStats.shtm page from the instance that you are seeing not update as expected?
-
OK here are the screen shots taken one after another.
The point values for 2501 cold water and energy.
-
The story gets weirder because the system began logging every minute at 11:13 on its own and the warnings about point reliability have gone away however it is ignoring the point settings which is set to log interval 15 minutes and is now logging every minute as the poll is set to 1 minute.
-
So I think the live point values fixed itself on the restart and the last post was in error because I was looking at cached values and not realizing this. it appears to be working perfect again now! I made changes to the data source names on Friday before this live value issue began happening and thought it might have been related. This is a production server so we don't like to restart but I guess a restart is required sometimes because it's working correctly now.
