Skip to main content
Skip table of contents

Open Collector 2024.10 Release Notes

October 2024 Release Details

The 2024.10 release of Open Collector requires Knowledge Base version 7.1.701.0 (or above).

Software Component

Version Number

New Version?

Open Collector

5.6.20

LRCTL Script

6.0.1

LRCTL Container

6.5.18

Yes

LRJQ

5.1.4

Metrics

6.0.7

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

Exabeam Case Beat

6.0.0

Yes

Generic Beat

6.2.0

Gmail Message Tracking Beat

6.0.5

Yes

GSuite Beat

6.0.4

Kafka Beat

6.0.7

Yes

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

New Features

Feature or Beat

Description

Relevant Documentation Updates

Exabeam Case Beat

A new beat has been added for the Exabeam Case Beat, allowing collection of logs from Alert by Exabeam.

Exabeam Case Beat

Resolved Issues

Bug ID

Release Notes

ENG-24578

The Google Message Tracking Beat no longer produces “panic” errors in certain situations despite being configured correctly.

ENG-51440

An issue with Open Collector commands causing panic runtime errors in certain situations 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).

JavaScript errors detected

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

If this problem persists, please contact our support.