| Resolution | Below are some suggested solutions for this scenario:
- Typically, the Windows Server event viewer Properties is set to "Overwrite events as needed (oldest events first)" with a "maximum log size (KB)". Confirm the "Overwrite events as needed (oldest events first)" is been used, and increase the "maximum log size (KB)" to keep the Windows event log for longer.
- Option #1 will not, however, solve the issue if the SA Log Collector can't or isn't configured to collect the logs fast enough. If option #1 does not rectify the situation, increase the collection rate for problem windows server in the SA GUI, Administration -> Services -> {Log Collector} -> Config
Event Sources tab
Select Windows and Config in the dropdown boxes.
Edit the problem Event Category, and open the Advanced
Look to increase the value for parameters: Max Duration Poll, and Max Events Per Cycle
Look to decrease the value for parameter: Polling Interval
Where setting:
Max Events Per Cycle = 0, Log Collector will collect as many events as it can in the Max Duration Poll time.
Polling Interval = -1, Log Collector will disable any pause between collection cycles.
- Alternately be certain to check each of the hosts, and be certain to set Debug to Off. This issue can be introduced by Debug being set to On or Verbose, and will slow down the ability to collect Windows event logs.
|
on Jun 14, 2016
