Log Collection Deployment: Troubleshoot

Document created by RSA Information Design and Development Employee on Jul 23, 2016Last modified by RSA Information Design and Development Employee on Sep 14, 2016
Version 4Show Document
  • View in full screen mode

This topic suggests how to resolve problems you may encounter during deployment

Security Analytics informs you of Log Collector problems or potential problems in the following two ways:

  • Log files.
  • Health and Wellness Monitoring view

Log Files

If you have an issue with a particular event source collection protocol, you can review debug logs to investigate this issue. Each event source has a Debug parameter that you can enable (set parameter to On or Verbose) to capture these logs.

Only enable debugging if you have a problem with this event source and you need to investigate this problem. If you have Debug enabled all the time it will adversely affect the performance of the Log Collector.

Security Analytics has a set of error messages associated with Log Collection that it includes in log files.

Health and Wellness Monitoring

Health and Wellness monitoring makes you aware of potential hardware and software problems in a timely manner so that you can avoid to outages. RSA recommends that you monitor the Log Collector statistical fields to make sure that the service is operating efficiently and is not at or near the maximum values you have configured. You can monitor the statistics described in the Administration > Health & Wellness view.


You are here: Log Collection Deployment Guide > Troubleshoot Log Collection Deployment