Since many/most people using tcollector are probably using the latest official tcollector release (1.3.2), which predates this patch, it wouldn't be surprising if most tcollector users are now experiencing this problem. You may consider getting 1.3.3 out the door ASAP, or doing a quick point release with just this change.
Oddly, this was harder for me to track down than it otherwise would have been, because I somehow did get one data point every hour or two, so my graphs weren't completely missing data -- the data was just very, very coarse (temporally speaking).
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub, or unsubscribe.