Cribl incident

Investigating: Potential problem with elastic destination

Notice Resolved View vendor source →

Cribl experienced a notice incident on March 27, 2023, lasting —. The incident has been resolved; the full update timeline is below.

Started
Mar 27, 2023, 10:13 AM UTC
Resolved
Feb 25, 2022, 10:30 PM UTC
Duration
—
Detected by Pingoru
Mar 27, 2023, 10:13 AM UTC

Update timeline

  1. resolved Mar 27, 2023, 10:13 AM UTC

    February 25, 2022 | 11:27PM The issue was determined to be a configuration format mismatch discovered in LogStream 3.3.0 for certain destinations which impacts egress data flow. This issue has been mitigated and throughput appears to be back to normal. Cribl Cloud Organizations are able to create their Elastic destinations and throughput has resumed for anyone impacted. Please note that you will not be able to create new InfluxDB destination until a patch of LogStream 3.3.0 is deployed. We thank you for your patience and understanding. February 25, 2022 | 10:53PM The team is still working on testing and verifying a fix to mitigate. We appreciate your patience if you have been impacted by this issue. February 25, 2022 | 10:19PM We are still investigating and working towards mitigation. At this time we know that at-least two destinations (elastic and influxdb) appear to be impacted after the Stream 3.3.0 update to Cribl Cloud organizations. The impact appears to be a drop in data throughput for these destinations as well as the inability to configure them as new destinations. More information will be posted as we confirm the total impact and verify a fix to mitigate. Thank you for you patience.