I used the threshold metric for the first time yesterday. First off, thanks
for adding it! Dario tells me it was brand new as of yesterday? He also
said it needs vetting?
One piece of feedback: combining threshold and 'time to threshold' seems to
make things more confusing. For example, when you select sum as an output,
you also get the sum of the time to threshold. That result -- like
92.7864 -- seems to be simply the sum of hours for the members of the
cohort. Knowing that it took the cohort a combined 92 hours to reach the
threshold isn't very actionable.
I had to reboot the redis server that stores all of your report results
today. This uncovered the very unpleasant truth that redis was never
backing up properly. Unfortunately, any report results that you had saved
are now lost. They can be rerun of course, but that gets me to the second
piece of bad news.
Even more frustratingly, I can't seem to get redis to come back up again.
We are working on this problem and will try to fix it ASAP. I will post
here once it's fixed.
Just a quick heads up, I've changed the way I report bytes added very
slightly. Instead of returning "null" when a user has no bytes added, I'm
now returning 0. This is to allow for more meaningful null values, like in
the case of time_to_threshold. So from now on, if you see a null value in
a metric report, it means that value will not be counted towards any
Hopes that makes things a bit clearer and here's the patchset if you're
We'll merge/deploy this shortly.