-
Suggestion
-
Resolution: Low Engagement
-
3
-
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
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.
- is related to
-
- Gathering Interest
[JRACLOUD-1335] Log Viewer from within 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.
Diego Alonso [Atlassian]
added a comment - 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
Diego Alonso [Atlassian]
added a comment - 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 
Jeff Turner
added a comment - 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).
Jeff Turner
added a comment - 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). Jeff Turner
added a comment - 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
added a comment - 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. 
Paul Smith
added a comment - 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.
Paul Smith
added a comment - 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. 
Brett Morgan
added a comment - 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.
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new features policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!