Skip to main content
Skip table of contents

Open Collector 2024.09 Release Notes

September 2024 Release Details

The 2024.09 release of Open Collector requires Knowledge Base version 7.1.699.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.7

Yes

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

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.5

Yes

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

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

Bug ID

Release Notes

ENG-61154

The Grafana instance has been updated to version 10.3.7 for Open Collector Metrics, promoting a more stable Open Collector experience.

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-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-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.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.