3

Closed

Restrict to a DateTime Range not working

description

I am gathering performance logs from 7AM to 7PM daily. When I try to restrict the PAL Tool analysis to a time within this an error is generated when the report is run. The PAL Tool report runs fine when I don't restrict the times. When I select the '.blg' file, the PAL Tool fills in the correct begin and end DateTimes for the entire log period. I was then simply changing the times to times within this range and running the report.
 
I have included the console output and error message below:
 
Transcript started, output file is C:\Users\JAMES_~1\AppData\Local\Temp\PAL.log
PAL v2.0.8 (http://www.codeplex.com/PAL)
Written by: Clint Huffman (clinth@microsoft.com) and other contributors.
Last Modified: 09/09/2011 22:27:02
The information and actions by this tool is provided "as is" and is intended for
information purposes only. The authors and contributors of this tool take no re
sponsibility for damages or losses incurred by use of this tool.
 
Your locale is set to: English (United Kingdom)
SCRIPT ARGUMENTS:
-Log C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_20111005-000
018\PAL_Microsoft_Internet_Information_Services_5.x_6.x_7.x.blg
-ThresholdFile C:\Program Files\PAL\PAL v2.0.8\AspDotNet.xml
-Interval AUTO
-OutputDir C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_201110
05-000018\PAL Report
-IsOutputHtml True
-HtmlOutputFileName [LogFileName]_PAL_ANALYSIS_[DateTimeStamp]jfjf.htm
-AllCounterStats False
-IsOutputXml False
-XmlOutputFileName [LogFileName]_PAL_ANALYSIS_[DateTimeStamp].xml
-BeginTime 05/10/2011 07:00:03
-EndTime 05/10/2011 07:30:03
 
 
Creating session working directory...
Creating directory "C:\Users\JAMES_~1\AppData\Local\Temp{b7b9a341-1aaa-4a16-965
4-0214c67e872a}"
Creating file "C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_201
11005-000018\PAL Report\PAL_Microsoft_Internet_Information_Services_5.x_6.x_7.x_
PAL_ANALYSIS_2011-10-06_15-15-53jfjf.htm"
Creating directory "C:\Users\James_Worthington\Desktop\aaa\UKDC1S10
1_20111005-000018\PAL Report\PAL_Microsoft_Internet_Information_Services_5.x_6.x
_7.x_PAL_ANALYSIS_2011-10-06_15-15-53jfjf\"
 
Threshold File Load History:
C:\Program Files\PAL\PAL v2.0.8\AspDotNet.xml
SystemOverview.xml
QuickSystemOverview.xml
DotNet.xml
 
Generating the counter list to filter on...Done
Removing duplicate counter expressions from counter list...Done
 
relog.exe "C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_2011100
5-000018\PAL_Microsoft_Internet_Information_Services_5.x_6.x_7.x.blg" -cf "C:\Us
ers\James_Worthington\AppData\Local\Temp{b7b9a341-1aaa-4a16-9654-0214c67e872a}\
CounterListFilter.txt" -f csv -o "C:\Users\James_Worthington\AppData\Local\Temp\
{b7b9a341-1aaa-4a16-9654-0214c67e872a}_FilteredPerfmonLog.csv" -y -b "10/05/201
1 07:00:03" -e "10/05/2011 07:30:03"

Input

File(s):
 C:\Users\James_Worthington\Desktop\aaa\UKDC1S101_20111005-000
018\PAL_Microsoft_Internet_Information_Services_5.x_6.x_7.x.blg (Binary)
Begin: 5/10/2011 7:00:03
End: 5/10/2011 19:00:03
Samples: 2881
Error: The time range specified has no overlap with the input logs.
MergeConvertFilterPerfmonLogs : [MergeConvertFilterPerfmonLogs] ERROR: Unable t
o find the converted log file:"C:\Users\James_Worthington\AppData\Local\Temp{b
7b9a341-1aaa-4a16-9654-0214c67e872a}_FilteredPerfmonLog.csv"
At C:\Program Files\PAL\PAL v2.0.8\PAL.ps1:5107 char:38
  • MergeConvertFilterPerfmonLogs <<<< -sPerfmonLogPaths $Log -BeginTime
    $global:BeginTime -EndTime $global:EndTime
    • CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
      tion
    • FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
      n,MergeConvertFilterPerfmonLogs
       
      MergeConvertFilterPerfmonLogs : Relog.exe failed to process the log. Review the
      results above this line. If relog.exe continues to fail, then try running Relo
      g.exe manually and/or contact Microsoft Customer Support Servers for support on
      Relog.exe only. PAL is not supported by Microsoft.
      At C:\Program Files\PAL\PAL v2.0.8\PAL.ps1:5107 char:38
  • MergeConvertFilterPerfmonLogs <<<< -sPerfmonLogPaths $Log -BeginTime
    $global:BeginTime -EndTime $global:EndTime
    • CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
      tion
    • FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
      n,MergeConvertFilterPerfmonLogs

file attachments

Closed Oct 3, 2013 at 6:35 PM by ClintH
English locale uses MM/DD/YYYY.

comments

ClintH wrote May 30, 2012 at 6:20 AM

Sorry for the delay in my response. This looks like a problem with no data for the dates you specified in the log. This is a problem with Relog.exe and your counter log. Relog.exe is part of the operating system and is supported by Microsoft. Are you still having this problem? If so, I am willing to help.

ClintH wrote May 30, 2012 at 7:15 AM

I recently fixed (really worked around) and issue with Relog.exe misinterpreting the date time ranges. I will release the fix in PAL v2.3.1 as an update release to v2.3. Please try it when I release it soon.

CodedSteve wrote Apr 25, 2013 at 12:46 PM

Hi,

I believe I'm getting the same problem when trying to look at at time range of 30 mins (11:30 to 12:00) from a log that was created over the course of 2 days.



Transcript started, output file is C:\Users\sallen1\AppData\Local\Temp\PAL.log
PAL v2.3.3 (http://www.codeplex.com/PAL)
Written by: Clint Huffman (clinth@microsoft.com) and other contributors.
Last Modified: 01/04/2013 13:44:32
The information and actions by this tool is provided "as is" and is intended for
information purposes only. The authors and contributors of this tool take no re
sponsibility for damages or losses incurred by use of this tool.

Your locale is set to: English (United Kingdom)
SCRIPT ARGUMENTS:
-Log C:\PAL\PAL_System_Overview.blg
-ThresholdFile C:\Program Files\PAL\PAL\SystemOverview.xml
-Interval AUTO
-OutputDir C:\PAL
-IsOutputHtml True
-HtmlOutputFileName [LogFileName]_PAL_ANALYSIS_[DateTimeStamp].htm
-AllCounterStats False
-IsOutputXml False
-XmlOutputFileName [LogFileName]_PAL_ANALYSIS_[DateTimeStamp].xml
-BeginTime 23/04/2013 23:30:30
-EndTime 23/04/2013 12:00:41


Creating session working directory...
Creating directory "C:\Users\sallen1\AppData\Local\Temp{cd20b8d5-3205-4538-9e0d
-eb9e26f842d4}"
Creating file "C:\PAL\PAL_System_Overview_PAL_ANALYSIS_2013-04-25_12-44-04.htm"
Creating directory "C:\PAL\PAL_System_Overview_PAL_ANALYSIS_2013-04-25_12-44-04\
"

Threshold File Load History:
C:\Program Files\PAL\PAL\SystemOverview.xml
QuickSystemOverview.xml
VMWare.xml
SystemOverview.xml

Generating the counter list to filter on...Done
Removing duplicate counter expressions from counter list...Done

relog.exe "C:\PAL\PAL_System_Overview.blg" -cf "C:\Users\sallen1\AppData\Local\T
emp{cd20b8d5-3205-4538-9e0d-eb9e26f842d4}\CounterListFilter.txt" -f csv -o "C:\
Users\sallen1\AppData\Local\Temp{cd20b8d5-3205-4538-9e0d-eb9e26f842d4}_Filtere
dPerfmonLog.csv" -y -b "23/04/2013 23:30:30" -e "23/04/2013 12:00:41"

Input

File(s):
 C:\PAL\PAL_System_Overview.blg (Binary)
Begin: 19/4/2013 13:39:30
End: 23/4/2013 11:54:41
Samples: 22622
Error: The time range specified has no overlap with the input logs.
MergeConvertFilterPerfmonLogs : [MergeConvertFilterPerfmonLogs] ERROR: Unable t
o find the converted log file:"C:\Users\sallen1\AppData\Local\Temp{cd20b8d5-32
05-4538-9e0d-eb9e26f842d4}_FilteredPerfmonLog.csv"
At C:\Program Files\PAL\PAL\PAL.ps1:5323 char:42
  • MergeConvertFilterPerfmonLogs <<<< -sPerfmonLogPaths $Log -Begin
    Time $global:BeginTime -EndTime $global:EndTime
    • CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
      tion
    • FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
      n,MergeConvertFilterPerfmonLogs
MergeConvertFilterPerfmonLogs : Relog.exe failed to process the log. Review the
results above this line. If relog.exe continues to fail, then try running Relo
g.exe manually and/or contact Microsoft Customer Support Servers for support on
Relog.exe only. PAL is not supported by Microsoft.
At C:\Program Files\PAL\PAL\PAL.ps1:5323 char:42
  • MergeConvertFilterPerfmonLogs <<<< -sPerfmonLogPaths $Log -Begin
    Time $global:BeginTime -EndTime $global:EndTime
    • CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorExcep
      tion
    • FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio
      n,MergeConvertFilterPerfmonLogs
C:\Program Files\PAL\PAL>

CodedSteve wrote Apr 25, 2013 at 12:50 PM

Looking at the log I've just realised my own mistake

23/04/2013 23:30:30" -e "23/04/2013 12:00:41

Apologies, the report is now running fine

ClintH wrote Apr 25, 2013 at 6:24 PM

Hi CodedSteve,

Can you send me the output of "Relog /?"? I want to see what the syntax shows for you on the -b and -e settings because it is likely dd/MM/yyyy for you and MM/dd/yyyy for me. With all of that said, Relog supports yyyy/MM/dd, so I'm hoping to just use that format as a standard.

Thank you,
-ClintH

ClintH wrote May 10, 2013 at 10:05 PM

Also, PAL needs at least 30 data point within the time range. Otherwise, it might refuse to do calculations on it. The log restriction tells PAL to create a new counter log that is within the time range provided. Then, PAL separates the new counter log into 30 time slices by default, so at least 30 data points are needed. Keep this in mind when using the time restrictions.

AceyMan wrote Jun 21, 2013 at 1:38 AM

I'm seeing a problem with "Restrict to a Date Time Range" as well, but it has (for me) a fix.

When I used the PAL wizard to select a range, the PAL tool ran AOK and made the html report without issue, but the range I chose was not honored -- the whole .blg was parsed. Hmmm.

The counters came from hosts with US dd/MM/yyyy date settings, but I run my workstation with ISO8601 date (yyyy-MM-dd) for the short form. After searching around, on a hunch I changed my workstation (where I was using the tool) to US format (which pained me greatly, heh), e.g., dd/MM/yyyy, and then re-ran the analysis on the same .blg files -- now the range I chose was honored. Whee.

This isn't a show stopper but it definitely is a puzzler for us right and proper souls who are ISO 8601 correct.

On a related note: when I used the 'Add to Queue' feature to restart the wizard from the top to select a new .blg for analysis, by choosing the new file the selected date range is reset. I suppose that makes sense, since the new log will most likely have different begin/end times, but it'd be slick to (optionally) preserve the chosen date range when choosing a new .blg to parse. For me, I'm analyzing a multi-tier web farm with MSSQL back end during load testing, so it's natural to only care about a common time window across every node in the farm; preserving the time range would be handy here.

Thanks for a great tool.

AceyMan wrote Jun 21, 2013 at 1:42 AM

(cannot find an edit feature)
Oops, I mistakenly wrote in my post: "US dd/MM/yyyy", naturally I meant "the counters came from hosts with US MM/dd/yyyy date settings."

Sorry about that. (My brain won't let me put a month ahead of a day. I get really bad cognitive dissonance... and I was even born in the US.... go figure).

ClintH wrote Jun 25, 2013 at 10:28 PM

Hi AceyMan,

I personally develop the PAL tool, so I don't have the resources to test it in a non-English-US environment and for that, I'm sorry. I have been considering adding advertising to this site as a revenue source where I can hire professional developers, but I'm still not sure about that. With that said, I always welcome contributions to the project in the form of code updates.

Thank you,