An update on this.  Basically, db1047, which is what everyone's querying to get EventLogging data, is still catching up.  The data there, at least for some schemas, is lagging and seems to have no new entries since "2014-04-27 12:10:00".  The data that EventLogging captured since then is safe and sound on db1048, which is where db1047 is trying to replicate from.  We will update this bug when the replication is all caught up:

So add yourselves to that bug and watch for it being Fixed.  Until then, dashboards and other things relying on this data will be out of date, but at least no longer erroring.