7.7.0 GA Release Notes

Expected Results: AIE Rules should not fire if the rule block relationship is not met.

Workaround: Change the Host (origin) or Host (impacted) fields to IP Address, and the AIE Rule works as expected.

Expected Results: AIE Summary Fields should be displayed on all AIE Notification emails.

Workaround: View the AIE Summary Fields in the Alarm instead of the Notification email.

Expected Results: AIE Rule Blocks should fire when they are triggered at the same time.

Workaround: As the behavior of simultaneous events is unpredictable and the use case for a 0-time interval is rare, LogRhythm does not plan to change this behavior at this time. To avoid the issue, set the evaluation period to 1 second.

Expected Results: These errors should not be reported in the AIE Engine log, but AIE is working and alarms are firing. 

Workaround: There is currently no workaround for this issue.

Expected Results: Poorly written AIE Rules should be suspended until they are altered and re-enabled.

Workaround: Rewrite the AIE Rule for better performance. Often, this involves adding filters, reducing log sources, and modifying the logic. Tuning an AIE Rule requires expertise, so contact LogRhythm Training, Professional Services, or a Sales Engineer to assist if necessary. Additional solutions to identify and monitor poorly performing rules are being developed for a future release.

Expected Results: AIE Rules fire as expected.

Workaround: There is no workaround at this time. LogRhythm is actively investigating the issue for a future release.

Expected Results: Alarms do not fire if a log is received for a Not Observed block.

Workaround: There is no workaround at this time. LogRhythm is investigating this issue for a future release.

Expected Results: These logs should be automatically purged after 7 days as defined.

Workaround: Sort by log date and delete all older logs.

Expected Results: Alarms should execute quickly as expected with other AIE Alarms.

Workaround: There is currently no workaround for this issue.

7.4.9,

7.4.10

Expected Results: The Alarming and Response Manager should able to send alarm notifications using any SMTP server and SSL authentication.

Workaround: There is currently no workaround for this issue.

Expected Results: Case API and Admin API should start when using any size certificate.

Workaround: Remove the server from the domain and reboot it. Verify that the 512-bit certificate has been removed, re-run the installers, and reboot. To avoid this issue, do not join the domain again or the certificate will be pushed out again. In addition, create a new certificate that uses a 384-bit (or less) hash or exclude the impacted system from the GPO that pushes the certificate.

Expected Results: The extra semicolon, which is an optional valid separator in a content-type header, should not prevent scripts from working upon upgrade.

Workaround: There is no workaround for this issue at this time. A solution is being investigated for a future release.

Expected Results: The processing of a log should be the same whether it is parsed in Rule Builder or MPE.

Workaround: Change the sub-rule to use a different tag, such as <Tag1>. If you are experiencing this issue, ensure that you are not using a custom Log Processing Policy and that there are no MPE timeouts. If issues persist, contact Technical Support and reference this bug number (DE1829) or its sister defect (DE1651).

Expected Results: When a search times out, a message should inform users and instruct them to re-run the search with a longer timeout.

Workaround: Increase the timeout on the query and re-run it.

Expected Results: Disabling Log Source Virtualization should not change the behavior of the System Monitor.

Workaround: This issue is caused by the scsm.ini file not being updated immediately. To work around it, refresh the Log Sources tab in the Client Console to force the .ini file to refresh.

Expected Results: Identity data appears in reports that contain those fields.

Workaround: Run an investigation to provide the same information.

Expected Results: All chosen fields should appear on the report if they contain data.

Workaround: Running the report as an investigation yields the expected results in the Network (Impacted) column. LogRhythm is actively working on a solution to this issue in a future release.

Expected Results: When exporting reports in .csv format, the column headers should not be repeated on each row.

Workaround: The report needs to be formatted to remove columns that show the column headers. In addition, LogRhythm data can be exported using Log Distribution Services (LDS).

Expected Results: Entities should be retireable and able to be hidden from view.

Workaround: Contact Technical Support to assist you in removing entities that are no longer needed.

Expected Results: When editing a report template, existing fields should remain unless they are explicitly removed.

Workaround: When editing a report template that contains the Normal Date field, add that field back to the template prior to saving it.

Expected Results: The Configuration Manager should load immediately and show the services in the correct state.

Workaround: The Configuration Manager will eventually load if given a little time.  When the services show down, a refresh of the Configuration Manager should show them correctly.  We are working on a resolution to this issue.

Expected Results: The Diagnostic logs should be tuned to alarm less frequently.

Workaround: There is no workaround for this issue at this time.

Expected Results: Alarms should continue to trigger and be displayed in the Web Console.

Workaround: Contact Technical Support for assistance, as there could be many reasons for this behavior beyond this defect. Support will help determine the root cause.

Expected Results: The Data Processor and Data Indexer connect to Service Registry after a reboot of the Platform Manager.

Workaround: Manually restart the API Gateway and Service Registry services on the Data Indexer and Data Processor after a reboot of the Platform Manager.

Expected Results: The "non-paged pool" should not increase and cause system performance issues.

Workaround: Restart the LogRhythm API Gateway service.

Expected Results: Autogrowth increases in larger increments so it does not cause fragmentation.

Workaround: Set the autogrowth settings to the following:

• EMDB: 256 MB
• Events: 1 GB
• Alarms: 256 MB
• LogMart: 256 MB
• CMDB: 256 MB

Expected Results: SQL deadlock issues should not cause a missed heartbeat.

Workaround: While there is no known workaround, this issue is being actively investigated for a solution.

Expected Results: Deadlocks should not cause a missed heartbeat alarm.

Workaround: While there is no workaround for this issue, LogRhythm is investigating a solution.

Expected Results: Authentication services for Web Console should not be interrupted by the change to the new tokens.

Workaround: Restarting the LogRhythm Authentication API on the Platform Manager mitigates this issue until the next time it occurs.

Expected Results: The Client Console should provide an alternate way to retrieve the data if Crystal Reports is not able to render it.

Workaround: Decrease the amount of data the report is trying to retrieve or export the data instead.

Expected Results: Scheduled reports should not be sent to disabled accounts.

Workaround: There is currently no workaround for this issue.

7.4.9,

7.4.10

Expected Results: The Job Manager should able to send scheduled reports using any SMTP server and SSL authentication.

Workaround: There is currently no workaround for this issue.

Expected Results: The report should show the accurate last backup time for each database.

Workaround: Review the backup information in SQL Server Management Studio.

Expected Results: Cache refresh and License enumeration does not interfere with the heartbeat. We should send heartbeat packets at the required interval.

Workaround: There is currently no workaround for this issue.

Expected Results: The AIE Data Provider service should start consistently and as expected. Failures should be consistently logged to alert when the service did not start correctly.

Workaround: Restart the Mediator service to allow the AIE Data Provider service to start. A more permanent solution to this issue is being evaluated for a future release.

Expected Results: Archives should process, seal, and move out of the Unprocessed Archives folder as long as the processing rate is at or below the system specification.

Workaround: Evaluate system sizing and consider an expansion to meet active load demands. In some systems, increasing the ArchiveSize setting in the Data Processor Advanced Properties to 51200 (from the default value of 10240) can help process archive files faster. If necessary, move large files out of the Unprocessed Archives folder to another drive and slowly feed them back in when the system is successfully processing the live data. A more permanent solution to this issue will be provided in a future release.

Expected Results: The TrueIdentity Sync Client should work for any number of users.

Workaround: While there is no workaround for this issue, the next release of the Sync Client will be able to support larger AD environments.

Expected Results: White space should be allowed in the OU/DC filter.

Workaround: While there is no workaround for this issue, LogRhythm is investigating a resolution for a future release.

Expected Results: Users should be able to scroll through all TrueIdentity records in the Web Console.

Workaround: Using filters to find specific data in the TrueIdentity page prevents the error message from showing and helps find data more quickly. LogRhythm is working on a resolution for a future release.

Expected Results: The Web Console should not time out when downloading large PCAP files.

Workaround: Change the time out setting in the Configuration Manager.

Expected Results: When copying widgets, all settings should remain.

Workaround: Users can add a new widget to the dashboard and configure it manually to work around this issue. This issue is still being actively investigated and will be resolved in a future release.

Expected Results: When users try to download a PCAP that is no longer available on disk, the error message should provide that detail instead of an unclassified failure.

Workaround: The error message will be changed in a future release. There are two simple troubleshooting steps to identify if the PCAP exists or if other issues are occurring in the integration: Log in to NetMon directly and verify if the selected PCAP has already aged out or should be available on disk. Recreate the API key for the selected NetMon and update the NetMon configuration in the Deployment Manager.

Expected Results: All data contained in the .csv export should be valid and match the data displayed in the Web Console.

Workaround: Export the same investigation from the Client Console or manually adjust the first and last date post export. LogRhythm is investigating a solution to this issue.

Expected Results: The Current Processing Rate widget shows all logs being processed.

Workaround: Resolve any log source issues that are causing old logs to be ingested, or use Grafana or Performance Counters to check the current processing rate.

Expected Results: The Download PCAP button appears when reviewing NetMon logs.

Workaround: Reload the frame with the Download PCAP button to activate it.

In certain circumstances, a SmartResponse action may fail to execute with an error: "No System Monitor Associated with execution target."

Expected Results: The SmartResponse Plugin should execute after selecting the System Monitor Agent.

Workaround: There is currently no workaround for this issue.

Expected Results: The remote web server should be enforcing HSTS.

Workaround: Configure the remote web server to use HSTS.

When the browser window is zoomed out, the Node-Link Graph on the Web Console dashboards may display an error: "Failed to establish logs subscription with the Web Console API." This is not related to the zoom functionality within the Node-Link Graph itself.

Expected Results: The Node-Link Graph should function regardless of the browser zoom level.

Workaround: Return the browser to 100% zoom and refresh the Web Console. 

Occasionally in multiple Web Console environments, AIE Drilldown does not export results or show data in the filters.

Expected Results: Drilldowns should always allow export of results and filters should always have data.

Workaround: Use the Client Console to drill down and export results.

When SSL Port In Redirects is set to Exclude in the Web Console configuration, links in Alarm and Case notification emails do not work.

Expected Results: The links sent in Case and Alarm notification emails should redirect to port 443 instead of 8443, as they are coming from an external location.

Workaround: Open the Web Console and manually find the Alarm or Case to review.

Scheduled reports that do not complete within an hour return only partial results without indication of additional results available.

Expected Results: The Job Manager should generate a message stating that the results were not complete and the report should indicate partial results.

Workaround: There is currently no workaround for this issue.

When clicking Case Evidence logs from the Case page, the Analyze window shows a Custom Filter that prevents the logs from displaying.

Expected Results: Clicking Case Evidence logs should open an Analyze page showing the logs selected.

Workaround: To show the logs, click the X next to the Custom Filter.

If FIPS and Integrated Security are enabled in a Disaster Recovery (DR) environment, the Admin API errors during startup because of a failure to connect to SQL during failover.

Expected Results: The Admin API should connect to SQL during failover.

Workaround: Manually change the Global IP to the Management IP. This may need to be done after each upgrade.

When running the LogRhythm Infrastructure Installer (LRII), you may receive the error: "No plan file found in LogRhythm Service Registry KV store." This is caused by the plan file not fully updating into the Consul KV store, and only happens in certain environments.

Expected Results: LRII should be able to run multiple times without affecting the plan file.

Workaround: For assistance with this issue, contact LogRhythm Technical Support.

In certain circumstances, Elasticsearch uses more memory than the set limit, causing performance issues on the server.

Expected Results: Elasticsearch should abide by the memory limit that is set.

Workaround: For a workaround, contact LogRhythm Technical Support.

Searches and drilldowns using Location lists do not return results.

Expected Results: Search results should return if using a Location list.

Workaround: Clone the original rule and replace the Location list with manual entries for the countries in Location (Origin).

After the Active Directory Sync, some Active Directory users may be disabled.

Expected Results: Only users who are disabled in Active Directory should be disabled within LogRhythm.

Workaround: Manually re-enable users by logging in to the Console as a Global Administrator or LogRhythm Admin user.

When using a Direction filter in the Web Console dashboard and drilling into any of the TopX widgets, the data shown in the Analyzer Grid contains logs that do not match the dashboard filter.

Expected Results: Drilling into data on a dashboard should not change the dashboard filter criteria.

Workaround: Reapply the dashboard filter.

In certain circumstances, customers with warm node indices may experience failed searches against those indices. This is due to Columbo being unable to close certain warm indices.

Expected Results: Columbo should handle the warm node indices correctly and allow searches.

Workaround: For assistance with this workaround, contact LogRhythm Technical Support.

When viewing the Metrics dashboard in Grafana, the Memory Used Percentage widget in the LR Metrics - Deployment View dashboard shows incorrect results for timeframes greater than three hours.

Expected Results: The aggregator in the widget query should use an average calculation instead of a sum calculation.

Workaround: For assistance with this workaround, see this knowledge article on the LogRhythm Community.

In certain circumstances, an Alarm does not associate with a SmartResponse Plugin and does not run the SmartResponse Plugin.

Expected Results: The SmartResponse Plugin should be triggered by any Alarm meeting the criteria.

Workaround: There is currently no workaround for this issue.