Telemetry seems flaky

[markwilkie]

Two examples:
https://dev.azure.com/dnceng/internal/_build/results?buildId=79531&_a=summary
https://dev.azure.com/dnceng/public/_build/results?buildId=77964

[markwilkie]

From AlexP:

Yea, this is a network issue sending telemetry:
2019-01-22T22:44:41.3775195Z F:\vsagent_temp\2692eb2b-9319-4269-9f7c-a48476b53649.ps1 : The underlying connection was closed: An unexpected error
2019-01-22T22:44:41.3776249Z occurred on a receive.

Some retry would probably help, but this is in powershell so retry is super annoying to write.

[natemcmaster]

It's failing aspnet builds now too.

2019-01-30T00:54:00.2625859Z ##[command]"C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe" -NoLogo -NoProfile -NonInteractive -ExecutionPolicy Unrestricted -Command ". 'F:\vsagent\_temp\03cdead3-fb69-4f2a-8027-d61c0d68aea2.ps1'"
2019-01-30T00:54:22.7269080Z Invoke-RestMethod : Unable to connect to the remote server
2019-01-30T00:54:22.7332922Z ##[error]PowerShell exited with code '1'.
2019-01-30T00:54:22.7363283Z At F:\vsagent\_temp\03cdead3-fb69-4f2a-8027-d61c0d68aea2.ps1:2 char:15
2019-01-30T00:54:22.7365033Z + ... orkItemId = Invoke-RestMethod -Uri "https://helix.dot.net/api/2018-03 ...
2019-01-30T00:54:22.7365085Z +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-01-30T00:54:22.7365125Z     + CategoryInfo          : NotSpecified: (:) [Invoke-RestMethod], WebException
2019-01-30T00:54:22.7365196Z     + FullyQualifiedErrorId : System.Net.WebException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand
2019-01-30T00:54:22.7365235Z  

Can we make telemetry fire and forget?