Trends not propagating to Master Node

[ataylo13]

I have a distributed setup and currently have 1 master and 3 child nodes. I have posted in other threads about how the "latest data" is not being send to master server. Even though the "latest data" is not there the graphs have the correct information on the master node. If you expand the graph to the last week the graph goes blank. If I log into the child node and perform the same task all of the information is there.

How can I get the trend data to the master server?

[xs-]

on the latest data thingy;
Each item record has a 'last value', 'last check', etc, field. These fields are used for latest data and, i think, some basic trigger evaluation on the master node. Node sync does not update these fields.

[steev]

having the same problem...

is there a fix for this? I really need the trend data on my master node so I can create graphs and maps using data from all of our data centers.

The trends data from child nodes *should* appear on their parent node, right? Am I wrong in that assumption?

[steev]

Upgrade to 1.8.4 fixed this for me.

I didn't see anything relevant in the release notes but found some things related in the bug tracking db so I thought I'd upgrade (newer is better, right?)

my trends data is now flowing from the children to the parent.

be careful tho, it seems like the upgrade changes the trigger logic slightly. Seems like triggers with UNKNOWN items now show up as PROBLEM, instead of just effectively being UNKNOWN themselves.