Cribl incident

Streams UI spins waiting for git

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:23 AM UTC
Resolved
Apr 09, 2022, 01:00 AM UTC
Duration
Detected by Pingoru
Mar 27, 2023, 10:23 AM UTC

Update timeline

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

    April 09, 2022 | 03:00AM Control Plane - AWS US West 2 has transitioned to Operational April 09, 2022 | 02:59AM The service is now in an operational state. We have identified a system performance issue and have increased capacity in order to mitigate the timeouts. Again, if you find that you are experiencing this issue please let us know by reaching out to support ([email protected]). We will continue monitoring for recurrence and take action if we find that your organization is affected. The team has a set of follow up actions and further changes to prevent this from happening in the future. We thank you and appreciate your patience as we work on this. Please refer to this page for all further updates. April 08, 2022 | 10:37PM Control Plane - AWS US West 2 has transitioned to Degraded (with workaround) April 08, 2022 | 10:36PM Control Plane - AWS US West 2 has transitioned to Unavailable Incident Status: At this time the service is still in a degraded state and our team is working on a fix to resolve the issue. What's the Issue: Some users may experience a hang (up to 7 mins) in the Stream UI when they attempt to access Stream from their cloud portal. What's the cause of this issue: At this time we suspect there is an API call to the remote Git repo that's hanging until it times out. Our engineering team is working to confirm the root cause and provide a fix. How does it affect me: If you find that you are experiencing this issue please let us know by reaching out to support ([email protected]). At the same time we are proactively monitoring for this issue and taking action if we find that your organization is affected. The action on our side involves a restart of the Stream Leader process which takes about 1 minute. Will I experience any Data Loss: You will not experience any data throughput issues You will not experience any data loss on any ingested data You will not experience any loss of data in logs (like audit, access etc..) You will lose monitoring data (metrics data that feeds the Stream dashboards like CPU Load, Events In/Out, Free memory etc..) due to the leader process restart. We thank you and appreciate your patience as we work on this. Please refer to the this status page for all further updates. April 08, 2022 | 07:08PM Control Plane - AWS US West 2 has transitioned to Degraded (with workaround) We are aware of the "spinning wheel" on Streams login from Cribl Cloud and are investigating. We are able to detect this issue when it occurs and mitigate. The experience for users is that there is a delay of 1-2 minutes during the transition of connecting to their Stream instance from Cribl Cloud workspace. We are continuing to look at the underlying root cause and fix. Thank you for your patience if you have been impacted by this.