Open Collector 2024.12 Release Notes

Open Collector

5.6.20

LRCTL Script

6.0.1

LRCTL Container

6.5.18

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

Generic Beat

6.2.0

Gmail Message Tracking Beat

6.0.5

GSuite Beat

6.0.4

Kafka Beat

6.0.7

Microsoft Graph API Beat

6.0.8

Yes

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

ENG-57414

The Salesforce Beat documentation has been updated to clarify that at the moment, only B2C audit logs can be collected.

ENG-62301

The MSGraph API Beat no longer generates “invalid response 400” errors in certain situations when the beat is correctly configured.

ENG-58560

The generic Open Collector notification messages, such as “heartbeat connection successful” and “Open Collector request URL,” have been updated to be more clear.

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