2:10 p.m.
Jesper Pedersen created LOGTOOL-62:
--------------------------------------
Summary: Log filtering tool
Key: LOGTOOL-62
URL: https://issues.jboss.org/browse/LOGTOOL-62
Project: Log Tool
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Reporter: Jesper Pedersen
Assignee: James Perkins
It would be nice to have a log filtering tool, which can help to extract / highlight log
statements in huge log files.
An idea could be to have a SQL like language in order to limit the number of lines as much
as possible
{noformat}
SELECT * FROM server.log WHERE CATEGORY = 'org.jboss.as' AND SEVERITY IN {FATAL OR
ERROR OR WARN} AND TIMESTAMP >= '12:42:00,000' AND CONTENT CONTAINS
'Something went wrong'
{noformat}
Having functions to select all / a defined number of lines after each hit, between
timestamps, and so on would be good.
--
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
2:23 p.m.
[
https://issues.jboss.org/browse/LOGTOOL-62?page=com.atlassian.jira.plugin...
]
David Lloyd commented on LOGTOOL-62:
------------------------------------
The format of log files is generally not a regular language, so it is impossible to
deterministically parse them. If logs are to be examined, the better solution is to
intercept them while they're still in a manageable format (i.e. write a Handler). For
such queries, a database-backed Handler seems apropos.
In any case this has nothing to do with the log tooling.
Log filtering tool
------------------
Key: LOGTOOL-62
URL: https://issues.jboss.org/browse/LOGTOOL-62
Project: Log Tool
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Jesper Pedersen
Assignee: James Perkins
It would be nice to have a log filtering tool, which can help to extract / highlight log
statements in huge log files.
An idea could be to have a SQL like language in order to limit the number of lines as
much as possible
{noformat}
SELECT * FROM server.log WHERE CATEGORY = 'org.jboss.as' AND SEVERITY IN {FATAL
OR ERROR OR WARN} AND TIMESTAMP >= '12:42:00,000' AND CONTENT CONTAINS
'Something went wrong'
{noformat}
Having functions to select all / a defined number of lines after each hit, between
timestamps, and so on would be good.
--
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
12:18 p.m.
[
https://issues.jboss.org/browse/LOGTOOL-62?page=com.atlassian.jira.plugin...
]
Gunnar Morling commented on LOGTOOL-62:
---------------------------------------
Jesper, you might consider to use a tool such as logstash or Splunk. They allow to
aggregate and index log files and perform searches as the one you describe.
Log filtering tool
------------------
Key: LOGTOOL-62
URL: https://issues.jboss.org/browse/LOGTOOL-62
Project: Log Tool
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Reporter: Jesper Pedersen
Assignee: James Perkins
It would be nice to have a log filtering tool, which can help to extract / highlight log
statements in huge log files.
An idea could be to have a SQL like language in order to limit the number of lines as
much as possible
{noformat}
SELECT * FROM server.log WHERE CATEGORY = 'org.jboss.as' AND SEVERITY IN {FATAL
OR ERROR OR WARN} AND TIMESTAMP >= '12:42:00,000' AND CONTENT CONTAINS
'Something went wrong'
{noformat}
Having functions to select all / a defined number of lines after each hit, between
timestamps, and so on would be good.
--
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
4401
days inactive
4421
days old
2 comments
3 participants
participants (3)
-
David Lloyd (JIRA) -
Gunnar Morling (JIRA)
-
Jesper Pedersen (JIRA)