The active_user_changes SQL script doesn't have an upper bound in the WHERE clause. The following subsets by time: rc_timestamp >= DATE_FORMAT(DATE_SUB(NOW(), INTERVAL 30 day), '%Y%m%d%H%i%s'), with the problem being that the value of the produced metric will be determined by when the script is ran in morning depending on how busy the cluster is rather than running in the morning and collecting the data within a distinct 30 day period. A new WHERE clause should likely be between the start of the day 30 days ago and midnight of the last evening.

This issue isn't critical, but it would be nice to check where we can do some improvements for data consistency :) If there's a group of other queries that should be checked with this I'd be happy to look into it all a bit more!