Matt Galbraith

Both staging and production "old" clusters are now cleaned up.

PR: https://dnceng.visualstudio.com/internal/_git/dotnet-helix-service/pullrequest/25665

https://dnceng.visualstudio.com/internal/_git/dotnet-helix-machines/pullrequest/25739 removes the autoscaler and vm cleaner from dotnet-helix-machines. I've purposefully self-blocked it here so that I can wait until the above PR merges before merging.

PR is merged and dead vm cleaner seems to be working as expected in staging. I'm moving this to rollout, where next week I will offline the remaining Azure function...

VM cleaner is running in prod with no issues and I've stopped the function app. I will delete it next week and this will be complete.

@ulisesh FYI; he reported to me today that the custom events in dotnet-eng have gone missing; I will be investigating that and trying to figure out what happened.

Everything is moved and happy, and I realized it's way harder to move to "one Kusto query to rule them all", so after discussing with @ChadNedzlek I am going to...

> I dunno...if they are internal msft, then it's possible we needed to add them to the dnceng-public Readers group? I don't see an update here, did you try adding...

There's, at least, three different network problems going on here: - netcorenativeassets DNS resolution - Timeouts talking to dotnetbuilds.azureedge.net (another storage account) - Curl failures reaching out to https://dotnet.microsoft.com/download/dotnet/scripts/v1/dotnet-install.sh @ilyas1974...

I don't think this issue is super useful to keep open. External dependencies are going to be occasionally flaky and there are bogus results coming up on this query anyways...