|
- Introducing: Log Parser Studio | Microsoft Community Hub
To download the Log Parser Studio, please see the attachment on this blog post Anyone who regularly uses Log Parser 2 2 knows just how useful and powerful
- More fun with Logparser and Exchange logs | Microsoft Community Hub
First, you'll need to turn on POP and IMAP logging in Exchange System Manager (this is for 2003 btw, I have no idea about 2007) The logparser command I used (for POP) was as follows: Logparser exe -i:evt -o:CSV "select distinct message into pop_user csv from \yourexchangeserverApplication where EventID = 1017 AND SourceName = 'POP3SVC'"
- More on Exchange ActiveSync Reporting with Log Parser - COM object . . .
In that blog we relied solely on LogParser using the IISW3C input format and your IIS Logs In this blog post, we take the capabilities of Log Parser one step further by leveraging the pluggable COM object interface We have put together an EAS specific Log Parser COM object to help make building queries much easier
- Log Parser Studio 2. 0 is now available | Microsoft Community Hub
@John B It's a tab being appended after the comma This appears to be a discrepancy between LP 2 2's interpretation of the CSV Output Format parameters data types and how PowerShell passes those parameters to LP 2 2
- LogParser date-time with another fields | Microsoft Community Hub
LogParser date-time with another fields Hello, My name is Tomas, I try to combine SELECT With date-time but when I try to organize by group and order I have this error:
- Log Parser - Identifying DOS attacks from IIS Logs
LogParser "SELECT {Log Field Name}, count(*) as Hits FROM {Log File Path} GROUP BY c-ip ORDER BY Hits DESC" - o:DataGrid If we find unusual number of requests from a client IP, we should verify whether the client is a normal client or a source of attack
- Advanced Exchange 2007 Transport Logs Troubleshooting using Log Parser . . .
Similar to examples mentioned earlier, the baseline Log Parser query for AGENT logs will look like this: logparser "select * from AGENT* log " -i:CSV -nSkipLines:4 -o:DATAGRID In order to get all types of rejection reasons I have came up with the bellow query: logparser "select case TO_INT(ReasonData) when NULL then 10 else ReasonData end as ReasonData2, count(*) as hits into agentreasonspread
- Log Parser Studio | Microsoft Community Hub
First published on MSDN on Mar 13, 2012 I occasionally use Log Parser 2 2 to do some work with IIS logs I recently stumbled across a tool to use in conjunction with Log Parser
|
|
|