Scalyr 장애 기록

1. 2026년 7월 6일 오후 8:24 UTCresolved

   이벤트 타임라인 7월 6, 06:58 UTC: 우리는 몇몇 고객을 충격시키는 자료 ingestion에 있는 지연의 인식입니다. 새로운 데이터의 외관에 지연을 경험할 수 있습니다. 7 월 6, 10 : 23 UTC : underlying 문제가 확인되었으며 엔지니어링 팀은 해결을 위해 적극적으로 노력하고 있습니다. 우리는 우리가 진행을하고 우리가 사건을 해결하기 때문에 지속적인 인내심을 주셔서 감사합니다. 7월 6, 15:50 UTC: 서비스는 복원되었습니다, 우리는 당신의 시스템의 건강을 검증하기 위해 노력하고 있습니다. data ingestion이 재시작되었지만, 여전히 처리되는 데이터의 일시적인 backlog가 있습니다. 시스템 잡음으로, 당신은 지연 경고에 큰 파도를 볼 수 있습니다. 이것은 예상된 행동입니다.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 10일 오후 4:51 UTCidentified

   Starting June 9 at 20:55 UTC, ingestion delays affected accounts on app.us1.dataset.com and app.eu1.dataset.com. The issue was identified, and a hotfix was deployed on June 10 at approximately 08:00 UTC. Ingestion has returned to normal in the EU environment. We are currently processing the remaining backlog in the US environment to restore normal performance.

2. 2026년 6월 11일 오후 4:37 UTCresolved

   As of June 11 at 8:11 UTC, the backlog events for accounts on app.us1.dataset.com have been completely processed, and the incident has been resolved.

1. 2026년 5월 8일 오후 10:31 UTCinvestigating

   We are currently investigating this issue.

2. 2026년 5월 8일 오후 10:50 UTCidentified

   We have identified an issue with a backend cluster that is currently disrupting event ingestion. Our engineering team is performing a system failover to restore normal operations.

3. 2026년 5월 9일 오전 12:07 UTCmonitoring

   Rebalancing our ingestion servers has stabilized the incoming data volume. Engineering is adding capacity to accelerate the processing of the data backlog. The impacted cluster has resumed ingestion at normal levels. All affected data has been queued since the beginning of the incident, so there is no data loss.

4. 2026년 5월 9일 오전 1:30 UTCresolved

   This incident has been resolved.

1. 2026년 4월 23일 오후 7:45 UTCmonitoring

   Apologies for the corrections. To clarify the scope of the incident mentioned in our previous post, the following environments were impacted: app.eu.scalyr.com, app.us1.dataset.com, and app.eu1.dataset.com.

2. 2026년 4월 23일 오후 7:47 UTCresolved

   This incident has been resolved.

1. 2026년 4월 23일 오후 7:34 UTCresolved

   Between 4:05 PM and 7:16 PM UTC, some DataSet customers may have experienced intermittent issues logging into the UI via SSO. This incident was limited strictly to the login interface; data ingestion and query capabilities were not impacted and remained fully operational throughout the event. Our engineering team has successfully mitigated the issue via a system rollback, and all SSO login services have been fully restored.

1. 2025년 9월 9일 오후 5:03 UTCinvestigating

   We are currently investigating an issue affecting both search and ingestion functionality on app.scalyr.com.

2. 2025년 9월 9일 오후 6:02 UTCidentified

   The issue has been identified and our Engineering teams are working to implement a fix. We will continue to provide updates on our progress.

3. 2025년 9월 9일 오후 8:29 UTCresolved

   All services have been fully restored and the incident is now resolved. We have validated that all systems are functioning normally. Thank you for your patience throughout this incident.

1. 2025년 1월 22일 오전 12:00 UTCidentified

   Ingestions were temporarily interrupted at approximately 8:30 PM GMT due to an authorization issue on the cluster. Recovery is currently underway, and users can expect the events to be backfilled slowly to their accounts

2. 2025년 1월 22일 오전 2:14 UTCresolved

   This incident has been resolved.

1. 2025년 1월 16일 오후 6:39 UTCinvestigating

   We are currently investigating this issue.

2. 2025년 1월 16일 오후 7:10 UTCinvestigating

   We are in the process of rolling back the change and restarting the affected servers. Some accounts may observe a gradual recovery of their logs.

3. 2025년 1월 16일 오후 7:48 UTCidentified

   A misconfiguration deployment caused server resource allocation issues. A rollback and server restart have been initiated to address the problem.

4. 2025년 1월 16일 오후 10:01 UTCmonitoring

   Recovery is currently in progress. The estimated time for full ingestion restoration is approximately 60 to 90 minutes from now.

5. 2025년 1월 17일 오전 12:22 UTCresolved

   The backlog data caused by the incident has been fully recovered in all regions

1. 2024년 10월 24일 오후 4:54 UTCinvestigating

   We are currently investigating the issue.

2. 2024년 10월 24일 오후 5:13 UTCidentified

   A misconfiguration deployed this morning prevented the servers from scaling up correctly. We are currently in the process of manually scaling up the servers to manage the ingestion volume effectively.

3. 2024년 10월 24일 오후 6:11 UTCidentified

   The aggressive scaling out of servers led to a 500 error when loading the page due to hitting the database connection limit. We are currently in the process of scaling the servers back in, and the error should be resolved shortly.

4. 2024년 10월 24일 오후 7:11 UTCmonitoring

   The UI should now be loading as expected. We have increased the database connection limit to accommodate more concurrent connections. The queue is in the process of recovering and is gradually processing the backlog of events.

5. 2024년 10월 24일 오후 11:49 UTCresolved

   This incident has been resolved.

1. 2024년 9월 26일 오후 7:36 UTCidentified

   Ingestion on app.us1.dataset.com returns 429 and 500 status codes since 2 pm GMT. A significant increase in ingestion has overloaded the cluster. The issue has been identified and we're working on a fix.

2. 2024년 9월 26일 오후 11:38 UTCresolved

   The ingestion pipeline and supporting systems are fully functional. While there is no suspected data loss it may take up to 24 hours to work through the backlog of data that has built up during the incident to be fully processed.

1. 2024년 9월 20일 오후 7:21 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 9월 20일 오후 7:34 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2024년 9월 20일 오후 8:33 UTCresolved

   This incident has been resolved.

1. 2024년 9월 12일 오후 6:29 UTCresolved

   Ingest for users on app.eu.scalyr.com was effectively halted at 3pm GMT. The issue was fully mitigated at 5:45pm GMT.

1. 2024년 9월 10일 오후 5:41 UTCidentified

   The correct build of the query servers failed to initialize, leading to performance issues with query execution. The root cause has been identified and the problem has been mitigated for users on app.scalyr.com. The recovery is still in progress for users on app.dataset.com

2. 2024년 9월 10일 오후 6:12 UTCmonitoring

   All query servers were restarted and query performance is back to normal

3. 2024년 9월 10일 오후 6:23 UTCresolved

   This incident has been resolved.

1. 2024년 8월 19일 오전 2:05 UTCinvestigating

   We are currently investigating this issue.

2. 2024년 8월 19일 오전 2:45 UTCidentified

   The issue has been identified and a fix is being implemented.

3. 2024년 8월 19일 오전 3:48 UTCresolved

   Ingestion traffic is now back to normal. The issue has been mitigated

1. 2024년 7월 12일 오후 6:57 UTCinvestigating

   The issue is currently under investigation

2. 2024년 7월 12일 오후 7:15 UTCmonitoring

   Queries are now functional on app.eu.scalyr.com after restarting the machines with the OOM issue.

3. 2024년 7월 12일 오후 7:39 UTCresolved

   This incident has been resolved.

1. 2024년 5월 2일 오후 4:59 UTCinvestigating

   We are investigating an ingestion issue on app.us1.dataset.com that began around 1450 GMT

2. 2024년 5월 2일 오후 6:52 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

3. 2024년 5월 2일 오후 11:28 UTCresolved

   Queue server ingestion delay has been resolved.

1. 2024년 5월 1일 오후 10:08 UTCresolved

   Failure to update the certification causes ingestion issues on the EU cluster. It has been reverted and the ingestion has resumed since 21:25 GMT

1. 2024년 4월 11일 오전 8:18 UTCinvestigating

   The issue is currently under investigation

2. 2024년 4월 11일 오전 8:25 UTCidentified

   The issue has been identified. A new endpoint in the last deployment broke the web application. A revert is in progress

3. 2024년 4월 11일 오전 8:55 UTCidentified

   The issue was affecting some users on app.scalyr.com and app.eu.scalyr.com. The service on those two endpoints have been restored. We are still in the process of restoring services on app.dataset.com and app.eu.dataset.com

4. 2024년 4월 11일 오전 9:39 UTCmonitoring

   All sites are now restored and the services are now back online

5. 2024년 4월 11일 오전 10:00 UTCresolved

   This incident has been resolved

1. 2024년 4월 10일 오후 9:48 UTCidentified

   Some users of app.scalyr.com, app.us1.dataset.com, and app.eu1.dataset.com are receiving intermittent 429 errors on search and dashboards. We have identified the issue and are working to remediate it.

2. 2024년 4월 10일 오후 10:42 UTCidentified

   A fix has been implemented and validation in progress.

3. 2024년 4월 10일 오후 11:30 UTCmonitoring

   A fix has been implemented and we are monitoring the results.

4. 2024년 4월 11일 오전 12:03 UTCresolved

   This incident has been resolved.

1. 2024년 3월 8일 오후 6:27 UTCresolved

   Users of app.us1.dataset.com experienced slow queries and errors between 16:50 UTC and 17:50 UTC. We have applied a fix to address the immediate issue and are implementing a code change as a long-term solution.