FYI, the event log doesn't last forever. It will eventually be purged. I believe it only shows you the last few hundred events. If there's a lot of activity, the record won't last long.

@Tim - Is there anyway, through repotools or otherwise to periodically dump/export the event logs for archival purposes?  Or even configure the retention period/size on the sever side?

I would assume one of the reasons for the auto-purge is to not let the event logs eat up too much space in the db, but this also creates a real hole in any audit capability for the solution.  Things such as the renaming of components and other objects (that are event logged) might need to be kept by organizations for a period of time (many years for some  companies).

-chris

Probably best to clarify or restate: "...this also creates a real hole in any audit capability for the solution." as an "overall" hole.  I do believe that with the work items, change sets in source control you can get a great deal of audit support with appropriate retention periods.  Just seems like there could be some way to better manage event logs long term than simply purging them away permanently.

I don't think it's customizable. The events come from the feed management used in all Jazz based products and it doesn't have a way to set the limit. I would suggest opening an enhancement or going through support to open an enhancement request. Users may be able to use the rss feed to archive the events if they want to customize something themselves.