I worked at SenSage, a company that creates a log-archiving/querying product (used by NSA/IRS/Dept-of-Treasury/Navy, banks, insurance companies, telcos, etc.). Our customers all had very good reasons for archiving logs:
* Real-time security never gives complete coverage
in an evolving electronic infrastructure ... there
always are vulnerabilities that are patched, new
services introduced whose risks aren't properly
understood at first, etc. Having a log archive
lets I.T. personnel look at history in case of
breaches to find how certain data was leaked,
or find what kinds of attacks were attempted.
This history informs I.T. personnel how to
improve their real-time security. It's an
essential part of the feedback system.
* The most dangerous data theft isn't done by
those penetrating a network from outside ... it's
done by unscrupulous insiders who have some
(needed) measure of access to the data. You need
to trust someone. But they're not always honest.
Trust, but verify. Archived log data is your
only recourse here ... and knowledge that every move
is recorded keeps insiders (if you choose to let them
know) honest.
* Yes, log archives help prosecute bad actors.
Log data archival is a big commitment, will take tons of disk space and some expensive software (for a large corporation), and should be more than simply a data sink. To be effective you need to be able to continually run standard and custom queries to see what's happening in your network.