This topic provides information about possible issues that Security Analytics users may encounter when working with ESA services. Look for explanations and solutions in this topic.
This section describes common issues that may occur while using ESA, and it suggests common solutions to these problems. You may be referred to other sections for more details, or you may be provided with a solution in the tables below.
Troubleshoot ESA Services
Troubleshoot ESA Database Issues
| ||The database that stores alerts has grown too large.||You may need to configure Alert database settings so that the database clears old alerts on a timely basis. |
For information on configuring these settings, see Configure ESA Storage in the Event Stream Analysis Configuration Guide. Once the database has become too large, you need to clear the alerts. Contact Customer Support to do this.
Troubleshoot RSA Live Rules for ESA
|I imported a group of rules from RSA Live, and now my ESA service is crashing. Why?||You may not have configured the parameters for the RSA Live rule to tune it for your environment.||Each rule in RSA Live has a description that includes the parameters you must configure and prerequisites for your environment. Review this description to see if the rule is appropriate for your environment. |
To ensure that you deploy rules safely in your environment, configure new rules as trial rules to test them in your environment. Trial rules add a safeguard for testing new rules. For details on this, see Deploy Rules as Trial Rules.
|I created a rule, and I checked the syntax. The rule looked fine. When I went to deploy the rule, I got an error. Why?||You may not have the correct meta to deploy the rule.||Check the Meta key references. You may not have the correct meta to deploy the rule.|
|I created a custom rule (via the Rule Builder or Advanced EPL), and my rule is not firing. Why?||You may have connectivity issues.||Check the 'Offered Rate' statistic on the Alerts > Configure > Services tab. |
If the offered rate is zero, then the ESA service is not receiving data from Concentrators. Validate the Concentrator connectivity. Go to Administration > Services, select your ESA and click on View > Config. Ensure the concentrator is enabled. Select the concentrator and click on test connection.
If the offered rate is not zero, the meta key name and type used in the rule likely doesn't match the meta key present in events. Check to see if the meta key name and type used in the rule is valid by searching for the meta key name in Alerts > Configure > Settings tab (Meta key references search).
|There may be a problem with the rule.||If a specific rule is not firing, go to Alert > Configure > Services to see if the rule was disabled. In the Deployed Rule Stats section, a rule that is disabled displays a clear enabled button (instead of the green enabled button).|
You can also check Events Matched field. Go to Alerts > Configure> Services. From there, you can see the number of events that were matched in the Events Matched column.
If no events matched, check the logic of your rule for errors. For example, check the syntax for uppercase and lowercase errors, and check the time window. If the rule still doesn't fire, consider simplifying the logic of the rule to see if it fires when there is less complexity.
Steps to Troubleshoot Memory Issues with an ESA Service Offline
Step 1: Verify that your Host is Running
The first step to troubleshooting is to ensure that your host is running. To do this, go to Administration > Hosts. If the host is down, the system parameters will not display (updating host information can sometimes be delayed), the Services displays in red, and the Updates field displays an error message.
If your host is down, contact your SA Administrator to restart it. Otherwise, go to Step 2.
Step 2: View Detailed Statistics in Health & Wellness
Once you are sure your ESA service is down, you can go to Health & Wellness to see where potential issues are occurring. The most common problem is that your ESA service is exceeding memory thresholds which causes it to stop or fail.
Go to Health & Wellness> Alarms to see if the ESA triggered any alarms. Look for the following alarms:
- ESA Overall Memory Utilization > 85%
- ESA Overall Memory Utilization > 95%
- ESA Service Stopped
Go to Health & Wellness > System Stats Browser to see details of your ESA performance. Select your host, and use the following filters to view the following statistics:
Host Component Category Statistic Example <your host> Host SystemInfo CPU Utilization 1.08% <your host> Host SystemInfo Memory Utilization 45.43% <your host> Host SystemInfo Used Memory 7.08 GB <your host> Host SystemInfo Total Memory 15.58 GB <your host> Host SystemInfo Uptime 77758, 1 week, 2 day... <your host> Event Stream Analysis ProcessInfo Memory Utilization 7.07 GB <your host> Event Stream Analysis ProcessInfo CPU Utilization 0.2% <your host> Event Stream Analysis JVM.Memory all Committed Heap Memory Usage 8.0 GB <your host> Event Stream Analysis ESA-Metrics Total ESA Memory Usage % 4.64%
If you are having a problem with memory or CPU utilization, continue to step 3.
Step 3: Bring up your ESA Services
- From Administration > Services, select the actions icon for your ESA service and choose start.
- Return to the ESA Service to troubleshoot which rules have created memory issues.
If your ESA service is stopping and restarting in a loop, you may need to call Customer Support to get the services to start.
If you are able to start your ESA service without a shutdown, continue to step 4.
Step 4: Check the Alerts and Events Volume
Once you are able to restart your ESA service without an immediate shutdown, you can review the stats for your rules to see which rules are consuming too many resources. Sometimes, ESA services fail because a rule is generating too many alerts or a rule is matching too many events. Check for both of these issues if you have determined that memory usage is causing your ESA service to shut down.
View Alert Summaries
Rules that generate a high volume of alerts can overwhelm the system and cause it to fail or restart. To view the alert summaries, go to Dashboard > Alerts > Summary. On the lower half of the screen, you can see the number of alerts generated for each rule in the Count field. If the number is significantly high for a particular rule, you need to disable the rule and rewrite it to be more efficient.
View Events Matched
Sometimes a rule matches too many events which can use up excessive memory. This typically occurs if you create a large event window where a great number of events accumulates without triggering an alert. These are a problem because each event is stored in memory while the rule waits for the alert to trigger. To check for this issue, go to Dashboard > Alerts > Services. From there, you can see the number of events that were matched in the Events Matched column. If there was a high number of events matched for a given rule, you can investigate the rule further to see if you can make it more efficient.
Step 5: Disable and Repair the Rule that Caused Issues
Once you have determined the rules that need to be rewritten, disable them and rewrite rules so that they don't generate such a high volume of alerts or events. For pointers on how to write more efficient rules, see Best Practices.
To disable rules:
- To disable rules, go to Alerts > Services, and select the rules you want to disable in the Deployed Rules Stats field.
- Select Disable to disable the rules.
To edit rules:
- To repair the rules, go to Alerts > Rules > Rule Library. Select the rule to edit, and click the actions icon .
- Select Edit.
- Edit the rule to be more efficient. For instructions on creating rules, see Add Rules to the Rule Library.
- Once you are satisfied with your rule, you can save the rule as a trial rule to ensure that any memory issues do not affect ESA services performance. To do this, follow the steps listed in Deploy Rules as Trial Rules.
To enable rules:
- To enable rules, go to Alerts > Services, and select the rules you want to enable in the Deployed Rules Stats field.
- Select Enable to enable the rules.
(Optional) Check the ESA Log Files for More Information
Once you verify that your services are down and some potential causes for the system going down, check to see if the service is stopping and restarting in a loop. To do this, go to the ESA logs. From the Administration > Services module, select your ESA service and click the actions icon and select View > Logs.
If you cannot access the ESA logs from the Security Analytics interface, you can SSH into the system and go to:opt/rsa/esa/logs/esa.log.