I'd like to be able to write a logfile parser that will tell me which ID's haven't finished in a log file (when the server crashes), and what SQL statements are taking the longest time. What's the easiest way to do this?2006-10-25 18:20:20,751 DEBUG [stuff][][] End Query: [Id: 1] [duration +: 96] 2006-10-25 18:20:20,762 DEBUG [stuff][][] Start Query: [Id: 2] [Descri +ption: ] [debug sql] <SQL Here> <more SQL> <more SQL> 2006-10-25 18:20:20,763 DEBUG [stuff][][] End Query: [Id: 2] [duration +: 1] 2006-10-25 18:20:20,764 DEBUG [stuff][][] Checking status of UserServi +ce 2006-10-25 18:20:20,764 DEBUG [stuff][][] Starting IntegrationService 2006-10-25 18:20:20,764 DEBUG [stuff][][] Service Started: Integration +Service 2006-10-25 18:20:20,776 DEBUG [stuff][][] Start Query: [Id: 3] [Descri +ption: ] [debug sql] SELECT
In reply to logfile parsing by phoneguy
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |