April 22, 2005
Circulation Reporting and Statistics Enhancements
We have finished the trials on a number of statistics enhancements that we will be rolling out very soon. As discussed here before, we will be providing a premium version of statistics for a monthly fee, and we are also enhancing the free statistics. At both levels, for example, we're introducing a number of commerce tracking capabilities for publishers running the Amazon service and others.
In providing these new detailed statistics, we are making a number of improvements and configuration changes to the way we calculate and store circulation statistics. One of the things we cannot do, of course, is take the system down for DB maintenance, ever, since we are constantly writing to the statistics tables as feeds are accessed, etc. We need to roll in changes on the fly with the system up and running.
As a result, starting this morning and probably through this weekend, we have been and will continue to be migrating changes into production while the system's running. In order to accomodate this migration, to make a long story short, we're going to continue calculating your circulation and traffic statistics, but we won't be writing them in real-time (as we do now) to the statistics tables that you access when you view your stats on FeedBurner. Therefore, over the next couple days, you will likely notice that your circulation numbers are low while we facilitate this migration. IMPORTANT: we are still gathering all your traffic data, and writing it to the reporting tables, and when the stats migrations are complete we will update your circulation data in the tables used for reporting to you. The only issue is that the stats aren't getting to the reporting tables in real time. Additionally, none of should have any impact on feed processing or feed data gathering on your behalf.
Comments
? Are we going through another blank spot in stats? I seem to have no traffic today (4/30)
I thought it was just me!
Whoops, thanks folks, you found a bug we accidentally introduced (as opposed to intentionally introduced?) with the code changes we made. We have fixed the bug and moved the fix to production. You should now see the correct value for today's stats. Thanks for the heads-up.
