distributed monitoring and "latest data"

[morgan]

Latest data does not appear to be updating properly from "remote nodes" on the local node. It appears "history" tables are properly updated.

This is 1.4.1.

The "queue" on the central node is also showing as all data being "pending" with the next check date being unix epoch 0.

Any insight?

[morgan]

It also looks as if the remote monitor isn't propagating data into it's latest data field(s).

Configuration was done from both Central Node (independantly) from the remote note (on the local web interfaces). It looks as if only the node that the config is done represents the "latest data" fields in the UI, but also the data (unless configured on the remote node) never gets updated or appears. If the remote node updates the data properly, the central node's UI is NOT reflecting this.

[morgan]

further research shows that there appears to be no nodesync for the lastvalue on remote nodes (which makes little sense), only events and history.

Something doesn't seem right but I could be just missing something.

[peter_field]

by design?

I have a feeling that this is by design... its the same for me too, except I can't even view/change the config from the master...

[Alexei]

Yes, currently there is no sync for operational data (like items' lastvalue, lastcheck, etc) between nodes. This is made in order to prevent excessive data exchange because this information is being updated very frequently.

I don't know if this will be changed any time soon. Perhaps this could be made optional...