Becouse the command-line interface for Microsoft Log Parser is not very intuitive, I have created Log Parser Lizard, a Microsoft Log Parser GUI tool for managing queries, exporting results to Excel, charts, etc… In addition I have added input filters for
log4net file format and SQL server T-SQL queries.
IMO, what we really need is a way to prompt the user for input.
Did you mean something like this. If you, enter query like (for example) ‘select * from <1> where Date = (@MyDate as date)', when you run it, the program will show dialog box for entering parameter @MyDate and pass it to the LogParser? Or
you have somethin else in mind?
Yes, it works for SQL Server errorlogs, set the input format to TEXTLINE and away you go. This gets around how slow Enterprise Manager is at opening the errorlogs and gives filtering and the ability to save the queries. A sample query is as follows:
select top 500 substr(text,0,22) as Date, substr(text,23,9) as Source, substr(text,32) as Message from '\\server\C$\instance\log\ERRORLOG.*' where Message not like '%Log backed up%' and Message not like '%DBCC TRACEON%'
and Message not like '%Login failed%' and Message not like '%Database backed up%' and Message not like '%Database log truncated%'
and Message not like '%DBCC CHECKDB%'
Just what I need. The ability to use variables for server and instance above so I can point at any of my production servers would be good. I've also got the above select to work natively as TSV input:
logparser.exe. "select top 500 STRCAT(STRCAT(DATE,' '), TIME) as Date, Source, Message from '\\server\C$\instance\log\ERRORLOG.*' where Message not like '%Log backed up%' and Message not like '%DBCC TRACEON%'
and Message not like '%Login failed%' and Message not like '%Database backed up%' and Message not like '%Database log truncated%'
and Message not like '%DBCC CHECKDB%' " -i:TSV -iseparator::spaces -iHeaderFile:c:\formatfile.txt -nskiplines:9
but when I open Queries.. and click on Properties... I get Exception has been thrown by the target of an invocation and then the values I enter don't get saved.
lizardlabs
40 Posts
New GUI tool for MS Log Parser, Log Parser Lizard
Dec 05, 2007 11:10 AM|LINK
Becouse the command-line interface for Microsoft Log Parser is not very intuitive, I have created Log Parser Lizard, a Microsoft Log Parser GUI tool for managing queries, exporting results to Excel, charts, etc… In addition I have added input filters for log4net file format and SQL server T-SQL queries.
You can download Log Parser Lizard from here www.lizardl.com
Microsoft.Net 2.0 is required.
lizardlabs
40 Posts
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Dec 17, 2007 07:28 AM|LINK
Ehemmm.... excuse me.... does anyon have tried the application? Any commnets....
tomkmvp
7657 Posts
MVP
Moderator
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Dec 21, 2007 11:58 AM|LINK
Is this tool web based? I'm looking for something that is web based ...
http://mvp.support.microsoft.com/
lizardlabs
40 Posts
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Dec 21, 2007 12:26 PM|LINK
No it is not web based, it is WinForms application based on .Net Framework 2.0. I dont know if there is web based solution for this.
juststeve
40 Posts
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Dec 22, 2007 01:37 PM|LINK
Nice to see some work being done for LP.
IMO, what we really need is a way to prompt the user for input.
lizardlabs
40 Posts
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Dec 26, 2007 12:47 PM|LINK
Did you mean something like this. If you, enter query like (for example) ‘select * from <1> where Date = (@MyDate as date)', when you run it, the program will show dialog box for entering parameter @MyDate and pass it to the LogParser? Or you have somethin else in mind?
ffnm
4 Posts
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Dec 27, 2007 04:35 AM|LINK
Great tool.
veritas
4 Posts
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Jan 07, 2008 02:52 PM|LINK
Looks nice, how do I point it at a server on the network? I'm looking to browse the SQL Server errorlogs and the event logs on a different box.
PS.
Small typing error under Help, should be Send Application Logs
lizardlabs
40 Posts
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Jan 08, 2008 10:09 AM|LINK
for evet logs: just add server name
ex. select * from \\APPSERVER\System
I'm not sure that you can parse SQL server error logs with MS Log Parser
veritas
4 Posts
Re: New GUI tool for MS Log Parser, Log Parser Lizard
Jan 08, 2008 03:14 PM|LINK
Yes, it works for SQL Server errorlogs, set the input format to TEXTLINE and away you go. This gets around how slow Enterprise Manager is at opening the errorlogs and gives filtering and the ability to save the queries. A sample query is as follows:
select top 500 substr(text,0,22) as Date, substr(text,23,9) as Source, substr(text,32) as Message from '\\server\C$\instance\log\ERRORLOG.*' where Message not like '%Log backed up%' and Message not like '%DBCC TRACEON%'
and Message not like '%Login failed%' and Message not like '%Database backed up%' and Message not like '%Database log truncated%'
and Message not like '%DBCC CHECKDB%'
Just what I need. The ability to use variables for server and instance above so I can point at any of my production servers would be good. I've also got the above select to work natively as TSV input:
logparser.exe. "select top 500 STRCAT(STRCAT(DATE,' '), TIME) as Date, Source, Message from '\\server\C$\instance\log\ERRORLOG.*' where Message not like '%Log backed up%' and Message not like '%DBCC TRACEON%'
and Message not like '%Login failed%' and Message not like '%Database backed up%' and Message not like '%Database log truncated%'
and Message not like '%DBCC CHECKDB%' " -i:TSV -iseparator::spaces -iHeaderFile:c:\formatfile.txt -nskiplines:9
but when I open Queries.. and click on Properties... I get Exception has been thrown by the target of an invocation and then the values I enter don't get saved.