Open Collector 2024.08 Release Notes
August 2024 Release Details
The 2024.08 release of Open Collector requires Knowledge Base version 7.1.697.0 (or above).
Software Component | Version Number | New Version? |
|---|---|---|
Open Collector | 5.6.20 | |
LRCTL Script | 6.0.1 | |
LRCTL Container | 6.5.17 | |
LRJQ | 5.1.4 | |
Metrics | 6.0.6 | |
OC Pipeline | 5.1.7 | |
OC-Admin | 6.0.15 | |
OC-DB | 6.0.2 | |
AWS S3 Beat | 6.2.2 | |
Azure Event Hubs Beat | 6.0.10 | |
Carbon Black Cloud Beat | 6.0.8 | Yes |
Cisco AMP Beat | 6.1.6 | |
Darktrace Beat | 6.0.0 | |
Duo Authentication Security Beat | 6.0.5 | |
Generic Beat | 6.2.0 | |
Gmail Message Tracking Beat | 6.0.4 | |
GSuite Beat | 6.0.4 | |
Kafka Beat | 6.0.6 | |
Microsoft Graph API Beat | 6.0.6 | |
Okta Beat | 6.0.5 | |
Prisma Cloud Beat | 6.0.2 | Yes |
Proofpoint Beat | 6.0.3 | |
PubSub Beat | 6.0.3 | |
Qualys FIM Beat | 6.0.5 | |
Salesforce Beat | 6.0.2 | |
Sophos Central Beat | 6.0.3 | |
Symantec WSS Beat | 6.0.3 | |
Webhook Beat | 6.1.7 |
Improvements
Feature or Beat | Description |
|---|---|
Carbon Black Beat | Due to API changes by Carbon Black, the Carbon Black beat has been refreshed and updated to use these new APIs in order to remain compatible and functional. |
Resolved Issues
Bug ID | Found in Version | Release Notes |
|---|---|---|
ENG-50585 | 2023.11 | An issue with the Prisma Cloud Beat displaying an HTTP 401 error in certain situations despite correct credentials being used has been resolved. |
ENG-60782 | 2024.06 | An issue with the Prisma Cloud Beat restarting and displaying an error in certain situations has been resolved. |
ENG-58540 | 2024.06 | An issue with the Carbon Black Beat’s API call has been resolved by the updated and refreshed APIs mentioned in the Improvements section. |
Security-Related Issues
Resolved security-related issues are available for customers to review on the Community.
Known Issues
Defect ID | Components | Release Notes |
|---|---|---|
ENG-49073 | System Monitor: JSON Parser | Issue: The System Monitor JSON Parser is timestamping logs with the time received rather than the time the event occurred. Expected Results: Logs will be correctly timestamped as when the event occurred. Workaround: Use the native Open Collector parsing (the old method). |
ENG-24578 | Beats: Google Message Tracking Beat | Issue: The GMT beat produces error messages when configured correctly. Expected Results: The Beat should not produce errors and should parse as expected. Workaround: There is currently no workaround for this issue. |
ENG-23908 | Beats: Generic Beat | Issue: Configuring the Generic Beat to collect SailPoint logs is causing “unknown certificate authority” errors. Expected Results: Beat setup should be successful with no errors. Workaround: There is currently no workaround for this issue. |