Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!aioe.org!newsfeed1.swip.net!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!spln!extra.newsguy.com!newsp.newsguy.com!news4 From: Michael Wojcik Newsgroups: comp.lang.java.programmer Subject: Re: analysis of java application logs Date: Thu, 26 May 2011 14:43:55 -0400 Organization: Micro Focus Lines: 19 Message-ID: References: NNTP-Posting-Host: p30f943019d6c58b05d3398578d40cfa96a1a6fa42838116f.newsdawg.com Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.5.0 In-Reply-To: Xref: x330-a1.tempe.blueboxinc.net comp.lang.java.programmer:4614 Daniele Futtorovic wrote: > > I'd call it (what I described): audit logging. I don't know if the > meaning of that term normally extends beyond databases, but I don't see > why it shouldn't. It's also used widely in security contexts. Most of the products I work on have multiple logging targets, for problem determination (which includes debugging), system history, auditing, and other operational uses. Sometimes these use different mechanisms, because they have different requirements - for example, security audit logs need to be protected, insofar as that's possible, from tampering by unauthorized users. -- Michael Wojcik Micro Focus Rhetoric & Writing, Michigan State University