> And personally, I think just having a stale value for stats-last-update is > sufficient for error checking, but we can squirrel away an error in a > stats-last- > error field if we want something more descriptive for clients, and just wipe > it > out on the next successful update. Not sure whether we should clear the > stats upon error or not, I think it might actually be useful to leave them. > If the > guest crashed because we ballooned away too much memory or something > for instance we'd be able to see the last value we logged.
I think the management app should cache the value if that is needed.
