July 2024 Release Details
The 2024.07 release of Open Collector requires Knowledge Base version 7.1.695.0 (or above).
|
Software Component |
Version Number |
New Version? |
|---|---|---|
|
Open Collector |
5.6.20 |
|
|
LRCTL Script |
6.0.1 |
|
|
LRCTL Container |
6.5.17 |
Yes |
|
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.7 |
|
|
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 |
Yes |
|
Okta Beat |
6.0.5 |
|
|
Prisma Cloud Beat |
6.0.1 |
|
|
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 |
|
Resolved Issues
|
Bug ID |
Found in Version |
Release Notes |
|---|---|---|
|
ENG-39921 |
2023.07 |
An issue with the MS Graph API Beat initially collecting logs but then stopping has been resolved, and logs are now collected as expected. |
|
ENG-37054 |
2023.06 |
An issue with the MS Graph API Beat not collecting logs as they are generated has been resolved. |
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. |
|
ENG-23895 |
Beats: Azure Event Hubs Beat |
Issue: Azure Defender logs are running very slow through the JQ pipeline. Expected Results: Azure Event Hubs Beat should collect without delay. Workaround: There is currently no workaround for this issue. |