Unsolved
This post is more than 5 years old
2 Posts
0
612
May 3rd, 2008 11:00
DCP - Recommended Collection Interval
I am troubleshooting a SYMM performance related issue and I want to ensure I have the correct collection interval set. I once heard that you should never go lower than 5 minutes as if you go lower, the numbers could be useless. Can anyone confirm or deny this and if you can confirm it, give an explanation of why?
Additionally, I am thinking of changin the daily interval from 15 minutes (default) to 5 minutes - can anyone think of a negative reason not to do this?
Thanks!
Additionally, I am thinking of changin the daily interval from 15 minutes (default) to 5 minutes - can anyone think of a negative reason not to do this?
Thanks!
No Events found!
malisetty
21 Posts
0
May 4th, 2008 22:00
Page 20-22:Data Collection Policy guidelines
Guideline D3 Disable WLA Revolving Data collection policy to conserve
resource utilization on agent host.
Guideline D4 Schedule WLA Analyst DCP for short duration only.
The WLA Analyst policy, designed to collect granular performance
data for troubleshooting a performance problem on one or a few
managed objects at a time, should only run for time periods that
sufficiently capture the event(s) necessary to identify problems. It is
not intended to be routinely run for all managed objects. In order to
achieve the desired level of data granularity, the data collection
frequency may be set at a higher rate than other DCPs. This high data
collection frequency can have a potential performance impact on the
target managed object, as well as the ControlCenter component hosts
for the collecting agent and the WLA Archiver. The degree of impact
depends on the type and size of the managed object and many other
factors.
Scenario: Symmetrix #37 is having a spike on IO rate between 2:00
and 3:30 pm. This Symmetrix is managed by a Storage Agent for
Symmetrix installed on host #46. Create one WLA Analyst policy at 2
minute interval for this Symmetrix. Apply a custom schedule to this
policy for a period of 1:00 pm to 4:00 pm. At 4:00 pm, the policy will
be automatically closed and data will be available in Performance
Manager for analysis.