Investigate Data Issues for PBI Report

[scbedd]

Paraphrased questions, not direct quotes.

From Javier:

The following missed SLA: why?

Azure/azure-sdk-for-go#5855
Azure/azure-cli#10762
Azure/azure-sdk-for-js#5944
Azure/azure-sdk-for-java#6081
Azure/azure-sdk-for-java#5220

Azure/azure-powershell#10301
Azure/azure-powershell#10634

Azure/azure-sdk-for-net#7454
Azure/azure-sdk-for-net#7921
Azure/azure-sdk-for-net#8490
Azure/azure-sdk-for-net#8498

Azure/azure-sdk-for-net#8561
Azure/azure-sdk-for-net#8627

Azure/azure-sdk-for-net#7933 - We became aware of it on Oct. 9th and we immediately answered

Azure/azure-sdk-for-net#8440 - There is a weekend in the middle. Unless we are instructed that we should work over the weekend for any GitHub issue like a Sev-2/1 CRI, we should account for weekends as 1 day.

Azure/azure-sdk-for-net#8788 - Same as above

Azure/azure-sdk-for-net#8434 This was technically a miss, but my comment is that the labels were added labels on Fri at 10:43 am and we replied on Monday. Difficult to spot new issues with a report that has a lag of 1 day (on Friday would not show) and with ZenHub not reporting all issues. We acted as soon as it was aware to us. We need better tooling that can allow us to monitor tens of repositories.

For Zach Alexander:

Why does Azure Automation only have a single issue in the past 30 days? And the one you have shows no comment, but we clearly commented. What is going on with this?

[scbedd]

Progress on Javier's questions:

• Eventhub Namespace Network Ruleset vnet rule Subnet ID returns ID with resource group name in lowercase azure-sdk-for-go#5855
  • v-Ajnava assigned, never commented.
• Secondary service bus - allow updates azure-cli#10762
  • axisc assigned, never commented.
• Cannot send messages, connection error after some period of time. Does not get reestablished. azure-sdk-for-js#5944
  • This one is definitely a bug. RCA: assigneeLogin is apparently a singular field. Looks like the value that we see in Kusto is essentially the first assignee. For this one, Ramya is an assignee and definitely responded in time, but we don't pick it up due to the data issue. I have filed Handle Multiple Assignees in PBI ServiceAttention Report #880 to track this.
• Cannot defer a message using the Azure Service Bus QueueClient Java API azure-sdk-for-java#6081
  • axisc assigned on October 29th. First comment November 4th.
• [BUG] Log4j.properties file in root jar file - azure-servicebus azure-sdk-for-java#5220
  • Combination. This one would also hit the assignee bug mentioned above, but even if that was working, we'd still fail SLA. binzywu, axisc, nemakam assigned, but the first response from any of them was October 25th. (bug filed on sep 9)
• New-AzEventHubAuthorizationRuleSASToken produces tokens with invalid date format azure-powershell#10301
  • Bug. This is an instance of Handle Multiple Assignees in PBI ServiceAttention Report #880. Second assignee apraovjr responded within 3 day SLA.
• Remove-AzEventHubNamespace with ResourceId errors with Object reference not set to an instance of an object. azure-powershell#10634
  • assignee apravojr first responded 13 days after creation.
• [BUG] Servicebus.ManagementClient enters permanent error state during failover azure-sdk-for-net#7454
  • Bug was filed on Wednesday Sep 2nd. Need to respond by Friday the 4th to meet SLA. The issue here is that we still count that as past the 72 hour SLA, even though they commented before the next failing business day.
• [FEATURE REQ] Service Bus: Support batching for operations other than Send azure-sdk-for-net#7921
  • Bug. Instance of Handle Multiple Assignees in PBI ServiceAttention Report #880
• [BUG] SessionHandlerOptions.MessageWaitTimeout allows zero value, but throws on ReceiveAsync azure-sdk-for-net#8490
  • Combination. Handle Multiple Assignees in PBI ServiceAttention Report #880 + first comment of any assignee > 7 days after creation. Would have failed SLA regardless.
• [BUG] Service Bus QueueClient stops receiving messages azure-sdk-for-net#8498
  • Combination. Handle Multiple Assignees in PBI ServiceAttention Report #880 + first comment of any assignee > 7 days after creation. Would have failed SLA regardless.
• [Service Bus] Detect connection status azure-sdk-for-net#8561
  • axisc assigned nov 1, first comment nov 10th.
• [BUG] External Azure account failing when used for Managed Identity in Visual Studio azure-sdk-for-net#8627
  • No comments by assignees
• [BUG] ServiceFabricProcessor throws an unexpected exception azure-sdk-for-net#7933
  • First created october 4th, would need to respond by the 6th.
• [FEATURE REQ] Support for safe batching with MessageSender azure-sdk-for-net#8440
  • No comments by assignees
• lot of ServiceBusCommunicationException getting logged in application insight with Microsoft.Azure.ServiceBus 4.1.1 azure-sdk-for-net#8788
  • No comments by assignees
• Expose MessageCount values in paged namespace queries azure-sdk-for-net#8434
  • No comments by assignees

So there is one issue. The Multiple Assignee Problem. Tracked in #880

This can be ameliorated by removing all the other assignees (other than the one who commented) and then adding them back. Should make the assigneeLogin field contain the one we want.