Home
%3CLINGO-SUB%20id%3D%22lingo-sub-1100571%22%20slang%3D%22en-US%22%3EExperiencing%20Data%20Access%20Issue%20for%20Azzure%20Monitor%20in%20East%20US%20Region%20-%2001%2F10%20-%20Investigating%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1100571%22%20slang%3D%22en-US%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Friday%2C%2010%20January%202020%2012%3A14%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20continue%20to%20investigate%20issues%20within%20Log%20Analytics%20and%20Application%20Insights.%20Some%20customers%20in%20EUS%20region%20continue%20to%20experience%20issues%20with%20data%20access%20from%20Azure%20portal%2C%20query%20failures%20in%20Azure%20Log%20analytics%20and%20delayed%20or%20missed%20alerts%20in%20Log%20Search%20Alerts.Initial%20findings%20indicate%20that%20the%20problem%20began%20at%2001%2F10%20~02%3A10%20UTC.%26nbsp%3B%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20Retry%20might%20help%3C%2FLI%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F10%2018%3A30%20UTC%3C%2FLI%3E%3C%2FUL%3E-Mohini%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Friday%2C%2010%20January%202020%2004%3A33%20UTC%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3EWe%20apologize%20for%20posting%20out%20the%20resolved%20communications%20earlier.%20We%20are%20still%20seeing%20customer%20impact%20in%20Application%20Insights%20and%20Log%20Analytics%20for%20East%20US%20Region.%20Some%20customers%20in%20East%20US%20Region%20may%20be%20experiencing%20issues%20with%20data%20access%20from%20Azure%20portal%2C%20query%20failures%20in%20Azure%20Log%20analytics%20and%20delayed%20or%20missed%20alerts%20in%20Log%20Search%20Alerts.%20We%20will%20send%20out%20the%20next%20update%20as%20and%20when%20we%20learn%20more.%20The%20issue%20got%20resurfaced%20as%20the%20maintenance%20activity%20for%20one%20of%20the%20backend%20service%20exceeded%20the%20expected%20threshold.%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CBR%20%2F%3E%3C%2FDIV%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CUL%3E%3CLI%3E%3CU%3EWork%20Around%3C%2FU%3E%3A%20Retry%20might%20work.%3C%2FLI%3E%3CLI%3E%3CU%20style%3D%22box-sizing%3A%20border-box%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3ENext%20Update%3C%2FU%3E%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20rgb(255%2C%20255%2C%20255)%3B%20color%3A%20rgb(0%2C%200%2C%200)%3B%20font-family%3A%20%22%20helvetica%3D%22%22%20neue%3D%22%22%3E%3A%20Before%2001%2F10%2011%3A00%20UTC%3C%2FSPAN%3E%3CB%3E%3C%2FB%3E%3CI%3E%3C%2FI%3E%3CU%3E%3C%2FU%3E%3CSUB%3E%3C%2FSUB%3E%3CSUP%3E%3C%2FSUP%3E%3CSTRIKE%3E%3C%2FSTRIKE%3E%3CBR%20%2F%3E%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jayadev%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EUpdate%3C%2FU%3E%3A%20Friday%2C%2010%20January%202020%2004%3A19%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe've%20confirmed%20that%20all%20systems%20are%20back%20to%20normal%20with%20no%20customer%20impact%20as%20of%2001%2F10%2C%2003%3A32%20UTC.%20Our%20logs%20show%20the%20incident%20started%20on%2001%2F10%2C%2002%3A10%20UTC%20and%20that%20during%20the%201%20hour%20and%2022%20minutes%20that%20it%20took%20to%20resolve%20the%20issue%20some%20customers%20in%20East%20US%20may%20have%20experienced%20issues%20with%20data%20access%20from%20Azure%20portal%2C%20query%20failures%20in%20Azure%20Log%20analytics%20and%20delayed%20or%20missed%20alerts%20in%20Log%20Search%20Alerts.%3CBR%20%2F%3E%3CUL%3E%3CLI%3E%3CU%3ERoot%20Cause%3C%2FU%3E%3A%20The%20failure%20was%20due%20to%20issues%20with%20our%20backend%20service.%3C%2FLI%3E%3CLI%3E%3CU%3EIncident%20Timeline%3C%2FU%3E%3A%201%20Hour%20%26amp%3B%2022%20minutes%20-%2001%2F10%2C%2002%3A10%20UTC%20through%2001%2F10%2C%2003%3A32%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20understand%20that%20customers%20rely%20on%20Azure%20Log%20Analytics%20as%20a%20critical%20service%20and%20apologize%20for%20any%20impact%20this%20incident%20caused.%3CBR%20%2F%3E%3CBR%20%2F%3E-Jayadev%3CBR%20%2F%3E%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CDIV%20style%3D%22font-size%3A14px%3B%22%3E%3CU%3EInitial%20Update%3C%2FU%3E%3A%20Friday%2C%2010%20January%202020%2003%3A32%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20are%20aware%20of%20issues%20within%20Log%20Analytics%20and%20are%20actively%20investigating.%20Customers%20in%20East%20US%20may%20experience%20issues%20with%20data%20access%20from%20Azure%20portal%2C%20query%20failures%20in%20Azure%20Log%20Analytics%20and%20delayed%20or%20missed%20alerts%20in%20Log%20Search%20Alerts.%3CUL%3E%3CLI%3E%3CU%3ENext%20Update%3C%2FU%3E%3A%20Before%2001%2F10%2008%3A00%20UTC%3C%2FLI%3E%3C%2FUL%3EWe%20are%20working%20hard%20to%20resolve%20this%20issue%20and%20apologize%20for%20any%20inconvenience.%3CBR%20%2F%3E-Jayadev%3C%2FDIV%3E%3CHR%20style%3D%22border-top-color%3Alightgray%22%20%2F%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1100571%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EApplication%20Insights%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAzure%20Log%20Analytics%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ELog%20Search%20Alerts%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Final Update: Friday, 10 January 2020 18:15 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/10, 07:00 UTC. Our logs show the incident started on 01/10, 02:10 UTC and that during the 4 hours and 50 minutes that it took to resolve the issue customers in EUS region experienced issues with data access from Azure portal, query failures in Application Insights and Log Analytics and also delayed or missed alerts in Log Search Alerts.
  • Root Cause: The failure was due to issue in one of the backend services.
  • Incident Timeline: 4 Hours & 50 minutes - 01/10, 02:10 UTC through 01/10, 07:00 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jayadev

Update: Friday, 10 January 2020 12:14 UTC

We continue to investigate issues within Log Analytics and Application Insights. Some customers in EUS region continue to experience issues with data access from Azure portal, query failures in Azure Log analytics and delayed or missed alerts in Log Search Alerts.Initial findings indicate that the problem began at 01/10 ~02:10 UTC. 
  • Work Around: Retry might help
  • Next Update: Before 01/10 18:30 UTC
-Mohini

Update: Friday, 10 January 2020 04:33 UTC

We apologize for posting out the resolved communications earlier. We are still seeing customer impact in Application Insights and Log Analytics for East US Region. Some customers in East US Region may be experiencing issues with data access from Azure portal, query failures in Azure Log analytics and delayed or missed alerts in Log Search Alerts. We will send out the next update as and when we learn more. The issue got resurfaced as the maintenance activity for one of the backend service exceeded the expected threshold.

  • Work Around: Retry might work.
  • Next Update: Before 01/10 11:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev

Update: Friday, 10 January 2020 04:19 UTC

We've confirmed that all systems are back to normal with no customer impact as of 01/10, 03:32 UTC. Our logs show the incident started on 01/10, 02:10 UTC and that during the 1 hour and 22 minutes that it took to resolve the issue some customers in East US may have experienced issues with data access from Azure portal, query failures in Azure Log analytics and delayed or missed alerts in Log Search Alerts.
  • Root Cause: The failure was due to issues with our backend service.
  • Incident Timeline: 1 Hour & 22 minutes - 01/10, 02:10 UTC through 01/10, 03:32 UTC
We understand that customers rely on Azure Log Analytics as a critical service and apologize for any impact this incident caused.

-Jayadev

Initial Update: Friday, 10 January 2020 03:32 UTC

We are aware of issues within Log Analytics and are actively investigating. Customers in East US may experience issues with data access from Azure portal, query failures in Azure Log Analytics and delayed or missed alerts in Log Search Alerts.
  • Next Update: Before 01/10 08:00 UTC
We are working hard to resolve this issue and apologize for any inconvenience.
-Jayadev