Solved!
Go to SolutionAbout Analyzer log gathering
Dear All,
I am confused with following points about Analyzer R26:
1. Do I need to receieve the performance data every 26 hours to get info everyday?
2. I can set the period to perform analyzer logging.
Will it keep the previouse 7 days data in flare OS if I set the period to 7 days?
I start a new task to do analyzer logging after it stopped, will it overwrite previouse data?
Is it possible that the analyzer logging will cause full space in flare OS?
Thanks for any sharing.
Dennis Dai
I am confused with following points about Analyzer R26:
1. Do I need to receieve the performance data every 26 hours to get info everyday?
2. I can set the period to perform analyzer logging.
Will it keep the previouse 7 days data in flare OS if I set the period to 7 days?
I start a new task to do analyzer logging after it stopped, will it overwrite previouse data?
Is it possible that the analyzer logging will cause full space in flare OS?
Thanks for any sharing.
Dennis Dai
- Sorry to resurrect this thread but I had a question about setting the interval to 600 seconds.
Would this ultimately be the same as me keeping my settings at real time interval @ 60 and archive time @ 120 and merging the files every day (ends up being 5 files a day)? From what I understood about the merging was that I keep the same number of data points and the merge function combines data points (most likely averages). It seems like setting to 600 would greatly simplify my process. - When you merge two SPA NAR files, the number of data pointsin the nerged file is the total of the two NARs. When you view the merged NAR file in analyzer, the points are compressed - the display will only show x number of points and the number in the merged NAR will be greater than what can be displayed - the points are not lost, just can't display.
You can dump the NARs to a CSV file and use a spreadsheet for graphing.
You can also change the Archive Interval to 600 seconds and get a NAR that covers 26 hours. But the time between each point will be 10 minutes rather than the 2 minutes - you'll see better data at 120 seconds, but will need to merge the NARs to see 24 hours (missing some of the points per the above).
You really only need to shorter interval if your looking for a problem.
glen
kelleg
6 Operator
•
4537 Posts
688
0
Posted September 4th, 2008 13:00
If you set the Archive Interval to 600 seconds, the amount of data collected in the Archive will be about 26 hours. If you create a new Archive every 24 hours, then you will have a full days worth of data. If you set the Interval to 60 seconds the archive will fill up in about 2.5 hours and then overwrite.
If you turn on Periodic Archiving, the array will create an Archive when the log is full and save the archive on the array. There is a location on the array that holds the archives (one on SPA and one on SPB). This location has a limit on the number of archives that it can hold, when this number is exceeded, the array will delete the oldest archive.
Using Periodic archiving will allow you to retrieve the Archives when you want.
You can set the time that data logging will run - from 1 day to forever.
If you turn off Periodic Archiving and disable the Stop After, the archive will always have the latest data - it will overwrite when it fills up - if interval is set to 600 seconds, after about 26 hours it will start to overwrite the oldest data. When you use this method, you can use naviseccli commands to create and retrieve archives every 24 hours. The command is:
naviseccli -h xxx analyzer -archiveretrieve (and a bunch of switches)
When you stop data logging, the SP will create an Archive with whatever data is in the log.
When you start data logging, you must wait for 10 collection intervals to elapse before you can create a new archive. If the Archive interval is set to 600 seconds, you must waiting 110 minutes before you can create an archive.
As always, check the on-line Help for more detailed information about using Analyzer.
glen