good to have this

Last Log for Jira does the job and is available for free on the Atlassian Marketplace: https://marketplace.atlassian.com/apps/1211604/last-log-for-jira

Not being able to view the application log from within the app is very cumbersome.

You may use freely our Log Custom Field available in the KCF-Aditional Custom fields plugin.

And:

1) The logs should be parsed to detect exceptions, which should be easily grouped (in case many of the same type are flooding the logs). The ability to acknowledge/accept an exception would be a nice extra.
2) The logs should be parsed against Hercules regular expressions to report known problems

This would help in cases where the reporter has JIRA admin rights but doesn't have access to the server filesystem (quite a common scenario).

Thanks for the offer Paul - we've got lots of other things requiring attention at the moment though, but we can always fish it out of Log4j's CVS if you commit it there.

I'm a log4j committer. I could whip you up a CyclicBuffer-based appender pretty easily if you want to add it for your release.

I'm going to be adding this into the log4j1.3 release anyway.

Velocity.properties is done.

We need to improve logging:

• change velocity.properties so that it uses log4j logging
• have a DEBUG level log that rolls over at 1M
• have a WARN log that doesn't get rolled & grows to unlimited size.