Problem: The CrowdStrike Falcon LogScale Destination's LogScale endpoint field is hidden from the 4.1.2 configuration modal, but can be restored. – v.4.1.2 – CrowdStrike Destination's 'LogScale endpoint' field hidden from UI Workaround: Treat infrequent rebalancing events as warn.įix: Depends on a change to the underlying kafkajs library. Problem: The Kafka, Azure Event Hubs, and Confluent Cloud Sources log REBALANCE_IN_PROGRESS events at the error level, even though only frequent rebalancing indicates a system-level or processing issue. – Multiple versions through 4.1.x – Kafka-based Sources' rebalancing is logged with exaggerated severity Workaround: Roll back to a previous stable version, such as 4.1.0. When this happens, you cannot manage or monitor Cribl Stream environments. Following a 4.1.1 or 4.1.2 upgrade, the Leader can become non-responsive to UI requests due to a steady 100% CPU utilization.

This change can have a negative impact in larger environments with many Worker Processes. Problem: In 4.1.1, to improve product security, we changed how we manage our RPC traffic from Leaders and Workers. – v.4.1.1–4.1.2 – Perf bug: RPC consuming excessive CPU compiling expressions This page lists known issues affecting Cribl Stream and/or Cribl Edge.

Unknown user streamcloud