Cribl: Investigating: Potential problem with elastic destination
Timeline of updates
- resolved
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.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).