Sid Krishna
Option 1: Expand on logic in azure-functions-host\src\WebJobs.Script.WebHost\Management to include event source information Option 2: Log these details at startup and have an analytics job that keeps a copy of startup...
@fabiocav I'm handling this one but will be reviewing the solution with you before submitting a PR.
At present the focus is for both triggers and input/output bindings (any place a customer configures a connection with another Azure service). Based on frequency of issues, the initial focus...
> @sidkri should we move this to the next sprint? Yes, I have updated it just now to the next sprint.
@cmenzi thanks for highlighting this behavior, we are modifying the logic to check if the HostId is set.
We should understand if this a regression and if so how it was introduced. 1. Did the serialization logic change? Let's understand where the Service Bus Message's serialized structure (over...
Confirmed that this is caused due to lack of support for managed identity based access by the detector. I'm looking into how to enhance the logic to account for this.
I have modified the risk alert logic so it should not report an issue when using managed identity anymore. @spmanjunath If possible, please verify that the issue is no longer...
Great, thanks for confirming @snicro and @spmanjunath - I will close this issue now.
Once this is done, we should identify Detectors that can benefit from the Function name column having a valid value.