[
https://issues.jboss.org/browse/AS7-2213?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-2213:
---------------------------------------
You're right. We -- well, really you ;) -- need to understand the requirements of this
and AS7-1311 better. There are two basic concerns I have here:
1) What is "the log"?
There can be as many "logs" as there are appenders people have created in the
system, including application specific ones. The output of some of them may not even be
accessible to the services we use to satisfy this JIRA and AS7-1311. And there's
nothing magical about server.log -- it's just the output of an appender we happen to
provide in our standard logging subsystem configurations. It may not exist, it may be
called foo.log, etc.
So any solution to this will need to provide an intuitive way for the user to tell us what
the logging of interest is.
2) How to parse "the log"?
Maybe this is no big deal. I'm sure it's not unsolvable since there are plenty of
log analysis tools out there. But if we support reporting back the contents of any
particular log file, we need to be able to parse those contents. To recognize what
sequence of text represents a new log entry vs a new line in an existing entry. And for
this JIRA we also need to understand where in the log record the severity information is
encoded.
My naive thinking for this issue was to cut through these two problems by having a custom
appender to track relevant output. But, such an approach doesn't help with the
AS7-1311 problem and has other flaws, so it's best to figure out solutions for both
this and AS7-1311.
Provide an operation to retrieve the last 10 errors from the log
----------------------------------------------------------------
Key: AS7-2213
URL:
https://issues.jboss.org/browse/AS7-2213
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management, Logging
Reporter: Heiko Braun
Assignee: James Perkins
Fix For: 7.2.0.Alpha1
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira