@AzureSupport - OK EUS CosmosDB appears to be coming back up now. But - why it appears we still keep having the same issue. No updates during the outage, no status in Resource Health - for four hours. More importantly - WE (Customers) found the issue and STILL no health alerts.
@AzureSupport "We acknowledge the problem. Some people may be experiencing..." as quickly as possible as a general first alert is fine. Resource Alerts that are four hours old are not alerts - they are information.
@AzureSupport Every RunBook should include assigning someone to provide updates to customers with as much, or as little, as possible as soon as possible. Remember: We too have customers.
Wrote a new LogAnalytics Alert which does not rely on CosmosDB. Used AppDependencies on DB Name using stdev on count of CosmosDB failures. Anything over 0 is an alert. That way we know CDB is down even if it can't tell us. #Azure#CosmosDB#down
Multiple CosmosDB down.
No Health Alert, Status, or Summary of the problem posted in Azure Resource Health
No information on root cause or time to recovery.
Single response from Azure: “We are aware of the issue and are working on it.”
We did not get as many alerts on the CosmosDB outage as I would like, from a monitoring perspective - especially since: no health alerts and db says online. Thinking... #Azure#CosmosDB#down
This is the second Azure outage in less than a week. Last one was APIM - just suddenly went offline, looked like a reboot. The last time we had a CosmosDB issue it was more than 4 hours of downtime. #Azure#CosmosDBDown
ERP and EDI Pros working on complex integration scenarios should take a look at Stedi's toolset and products. The capabilities are amazing and costs incredibly affordable. stedi.com#EDI#ERP#Microsoft365
NotreDame only on Peakock today = No NotreDame Football today. I am not paying for another streaming service just because NotreDame got in bed with one of them. #NoNDFootballToday