New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-1335
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Scott Farquhar [Atlassian]
Votes: 2
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JIRA

Log Viewer from within JIRA

Created: 18/Feb/03 05:30 PM   Updated: 18/Jun/08 02:06 AM
Component/s: Extensions
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 
Reference
 

Participants: Brett Morgan, Jeff Turner [Atlassian], Paul Smith and Scott Farquhar [Atlassian]
Since last comment: 39 weeks, 2 days ago
Labels: support_improvement


 Description  « Hide
a) Make logging easier to configure from within application. I should be able to change logging levels at runtime.

b) Be able to view logs from within JIRA. Perhaps use a file viewer, or a 'memory appender' to achieve this.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Scott Farquhar [Atlassian] added a comment - 28/Mar/03 12:07 AM
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.

Brett Morgan added a comment - 30/Mar/03 10:45 PM
Velocity.properties is done.

Paul Smith added a comment - 26/Oct/04 03:26 AM
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.


Jeff Turner [Atlassian] added a comment - 27/Oct/04 12:36 AM
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.

Jeff Turner [Atlassian] added a comment - 28/Nov/07 09:22 PM
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).