>>>>> On Thu, 6 Jul 2017 15:21:56 -0500, Doug Bell <d...@preaction.me> said:
> The API I had everyone test was a backwards-compatibility API. We will > gather data at multiple addresses, yes, but they all will feed to the > same database. It's important that the fast-matrix stays operational, > so the new API has a log.txt view same as the old API. The new log.txt > reads from the shared database so that no matter how the data comes > in, the fast-matrix will be able to pick it up. It's still the raw, > unprocessed data, so any problems with backend processing will not > hold up the fast-matrix data feed. (this is it, and it's slow, but it > will be behind a Fastly cache and I'll do other things if necessary: > http://metabase-beta.cpantesters.org/tail/log.txt) Just to make sure I did read that right. Are you saying [ ] fast matrix can continue to read http://metabase.cpantesters.org/tail/log.txt or are you saying [ ] fast matrix needs to switch to http://metabase-beta.cpantesters.org/tail/log.txt And do you have an idea why there might be the discrepancy of ~800000 reports in fast-matrix and ~1M in matrix in the last 4 weeks? If http://metabase.cpantesters.org/tail/log.txt is now significantly slower than it was, that would explain it, it might indeed lead to data loss. -- andreas
