When's event sourcing actually worth the extra effort for keeping track of state?

I've been looking into event sourcing a bit more lately, and I'm trying to figure out where it actually works best, not just the stuff you read in books. Sure, a complete audit log and easier historical searches sound great, but dealing with event stores, eventual consistency, and how event schemas change over time feels like a huge pain. For most basic apps, it just seems like too much. Are there situations or kinds of systems where the good parts really make up for all that extra work, making it the right way to go? What kinds of tough problems does it fix that are super hard with regular state management?