Eric Huggins

[Eric Huggins @Ehuggz1]

@antigravity I've uninstalled AG due to internal errors not recognizing my PRO licenses (both Corporate and personal). Privacy matters, I cannot use FREE.

[Eric Huggins @Ehuggz1]

#AlexaPlus "AlexaPlus is temporarily unavailable."

[Eric Huggins @Ehuggz1]

@AzureSupport Azure Portal interaction, saving changes, reviewing updates is extra-ordinarily slow. #EUS

[Eric Huggins @Ehuggz1]

LogAnalytics in the Azure Portal is not displaying any data after running a query. @AzureSupport

[Eric Huggins @Ehuggz1]

@AzureSupport Woke up to Database Down issues in East US after being offline for a few hours. #AzureOutage #AzureSQL

[Eric Huggins @Ehuggz1]

@AzureSupport Metrics in EastUS visible again. About 30 minutes blind. That was weird. #AzureMonitor.

[Eric Huggins @Ehuggz1]

@AzureSupport 100% Azure Monitor, Application Insights, LogAnalytics telemetry ceased presenting data at roughly 2:11 pm Eastern. Completely blind on SAAS operation. EastUS #AzureMonitor #AzureDown

[Eric Huggins @Ehuggz1]

Is this what third-shift in the Cloud is like these days. Working in Portal on Azure Runbooks, and then poof - CRAWLING! #Azure

[Eric Huggins @Ehuggz1]

@AzureSupport What happened to the Azure Portal. It was fine until about 11:30pm EST and then - poof. CRAWLING. #Azure

[Eric Huggins @Ehuggz1]

What just happened to the #AzurePortal. It is SOOOO slow!

[Eric Huggins @Ehuggz1]

@AzureApiMgmt Is there a way to capture the status of an APIM backup using the powershell command Backup-AzApiManagement? Command stops on completion, adding -PassThru returns information about the instance, not the operation, errors are not usably returned #AzureApiMgmt #Azure

[Eric Huggins @Ehuggz1]

@AzureSupport Azure P2S VPN connections unresponsive. No Errors, just no connection #Azure #AzureVPNGateway #AzureP2S

[Eric Huggins @Ehuggz1]

@AzureSupport @AzureSupport Anyone reporting issues connecting to EastUS Azure VPN? We are getting no response from multiple locations when connecting via OpenVPN.

[Eric Huggins @Ehuggz1]

@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.

[Eric Huggins @Ehuggz1]

@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.

[Eric Huggins @Ehuggz1]

@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.

[Eric Huggins @Ehuggz1]

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

[Eric Huggins @Ehuggz1]

LOL - Just got a health status alert on CosmosDB Outage. 15 min AFTER we are up. #Azure #CosmosDB #down

[Eric Huggins @Ehuggz1]

@BG5USN @Azure @AzureCosmosDB That depends on your config - but... at least one person reported multi-region live-live with auto-failover was a non-starter tonight. THAT's not supposed to happen.

[Eric Huggins @Ehuggz1]

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

[Eric Huggins @Ehuggz1]

@neilio42 @BG5USN @Azure @AzureCosmosDB Definitely.