Skip to main content
Skip table of contents

Open Collector 2024.06 Release Notes

June 2024 Release Details

The 2024.06 release of Open Collector requires Knowledge Base version 7.1.692.0 (or above).

Software Component

Version Number

New Version?

Open Collector

5.6.20

LRCTL Script

6.0.1

LRCTL Container

6.5.16

LRJQ

5.1.4

Metrics

6.0.6

Yes

OC Pipeline

5.1.7

OC-Admin

6.0.15

Yes

OC-DB

6.0.2

AWS S3 Beat

6.2.2

Azure Event Hubs Beat

6.0.10

Yes

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

Yes

GSuite Beat

6.0.4

Kafka Beat

6.0.6

Microsoft Graph API Beat

6.0.5

Okta Beat

6.0.5

Yes

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

Improvements

Feature or Beat

Description

Relevant Documentation Updates

Okta Beat

Okta Beat log sources have been updated to prepare for Okta’s upcoming 28 June change to stop processing requests with malformed syntax.

N/A

Gmail Message Tracking Beat

Due to a change by Google to its Gmail Message Tracking logs, the Gmail Message Tracking Beat has been updated to successfully continue collecting logs without issue.

N/A

Security-Related Issues

Resolved security-related issues are available for customers to review on the Community.

Known Issues

Defect ID

Components

Release Notes

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

Beats: MSGraph API Beat

Issue: MSGraph API Beat collects sign-in logs in bursts of 100k and then stops collecting.

Expected Results: Logs should collect as they are generated.

Workaround: There is currently no workaround for this issue.

ENG-39921

Beats: MSGraph API Beat

Issue: MS Graph API Beat initially collects Azure AD logs, but then immediately stops and no further logs are collected.

Expected Results: The MS Graph API Beat should continue to collect Azure AD logs as expected.

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.

JavaScript errors detected

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

If this problem persists, please contact our support.