Cribl: Splunk Single Instance and LB Unexpectedly Closing Connections
Affected components: AWS US East 1 (Virginia) - Data Plane (Workers)Data Plane (Workers)
Timeline of updates
- identified
The issue has been identified and a fix is being implemented.
- identified
Status: We have identified an issue in Stream version 4.8.0, where Splunk Single Instance and Splunk Load Balanced Destinations mistakenly detected that the downstream Splunk instance is frequently shutting down. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide updates every 60 minutes. Cribl Support is available to answer questions via email at support@cribl.io. Thank You for being a Cribl.Cloud customer.
- identified
Status: We're continuing to review the issue and are working to address it as soon as possible. To mitigate the issue in the meantime, set S2S version to v4. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide an update tomorrow morning at 8 AM EDT (Aug 15). Cribl Support is available to answer questions via email at support@cribl.io.
- identified
Status: We have identified a fix and plan on making it available today, within the next few hours. To mitigate the issue in the meantime, set S2S version to v4. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide updates every 60 mins. Cribl Support is available to answer questions via email at support@cribl.io.
- identified
Status: We have started to roll out the fix to addresss the issue. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide updates every 60 mins. Cribl Support is available to answer questions via email at support@cribl.io.
- identified
Status: We're continuing to roll out the fix to addresss the issue. Customer Impact: Stream and Edge Nodes are not able to connect to the Splunk destination. This incident affects: Cribl.Cloud Stream and Edge. Customer Splunk destination data streams are affected by this incident. Next Update: We will provide updates every 60 mins. Cribl Support is available to answer questions via email at support@cribl.io.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).