v.3.5.4 Release

October 13, 2022 · 3 min read
Michael Katz
Staff Technical Writer

2022-10-13 – Cribl Stream 3.5.4 | Maintenance Release | Edge 3.5.4 release notes are here.

New Features

This release provides the following improvements:

CRIBL-12569 On the Cribl TCP and Cribl HTTP Source/Destination pairs, we’ve relaxed format matching on the Leader’s hostname between the Leader versus Worker Nodes, and between the Nodes hosting Source versus Destination configs.

CRIBL-12662 On multiple Sources, we’ve increased the maximum allowed Event breaker buffer timeout value from 10 minutes to 12 hours. The default remains 1,000 milliseconds (1 second).

Breaking Change

CRIBL-7310 To prevent Worker Nodes from failing on incompatible configurations, we’ve introduced three new behaviors. These will make data throughput more resilient, but might enforce more-frequent (automated or explicit) upgrades to Workers’ Stream versions:

  • The Stream Leader will block configuration deployments to Worker Nodes running an earlier Stream version that’s incompatible with the new configs. The Leader will prompt you to upgrade these Nodes to a compatible version. In this 3.5.4 release, the Leader will test whether Workers are running at least v.3.5.0.
  • If Workers detect a Source or Destination type for which they have no supporting configuration, they will ignore (skip initializing) that integration, rather than failing.
  • For unsupported Destination types, Workers will create a temporary placeholder Destination, but will exert Blocking backpressure until the configuration is updated. You will see a warning of the form: Skipping configuring Destination...due to unrecognized type.

Deprecation Notices

Cribl.Cloud-managed Workers’ ARN (Amazon Resource Name) format will change after October 26, 2022. You must update any corresponding IAM roles to the new format.

Through that date, your Cribl.Cloud portal’s ⚙️ Network Settings > Trust tab will show two Worker ARNs, in these formats:

arn:aws:iam::000123456789:role/main-default
arn:aws:iam::000123456789:role/worker-in.logstream

Please bookmark both, but update your AWS account’s IAM role to match the main‑default variant. After October 26, Cribl will support only this format (and the Trust tab will show only this format). Details here on how to update your IAM role.

The following resources are already badged Deprecated, and Cribl will fully remove them from our next major release in November 2022. Please plan to transition your configurations accordingly.

Also in the November 2022 release, Cribl will remove the Intercom (support) chat widget from the lower-right corner of all on-prem and Cribl.Cloud deployments. For other ways to contact support, please see Working with Cribl Support.

Corrections

This release includes the following fixes:

CRIBL-12078 Corrected CloudWatch Logs Destination sequenceToken errors in distributed deployments.

CRIBL-10984 Metrics Data Source now validates fields for allowed characters.

CRIBL-12600, CRIBL-12613, CRIBL-12684, CRIBL-12693, CRIBL-12489 Corrected erroneously canceled Collection tasks and closed Collectors, and corrected resulting discrepancies in reported events.

CRIBL-12206 Corrected Filesystem Collector’s discrepancy between number of events discovered versus collected.

CRIBL-12653 Azure Blob Collector now provides options to disable Tags (and metadata) when using Secure Access Signatures with incompatible Storage Accounts.

CRIBL-12718 Corrected Failed to create diagnostic bundle ... size mismatch errors.