.Net: Monitor & Troubleshoot the Semantic Kernel C# SDK using the KernelFunction

[markbartolocodit]

.Net: Observability

We are using the Semantic Kernel C# SDK, but having some troubles identifying the possibilities to monitor & troubleshoot this solution.

We are using a KernelFunction using OpenAI and within that, the Azure OpenAI is throwing 429's.

Nevertheless, it seems that this is captured within the code of the Semantic Kernel & we cannot distinguish the issues when we get back the result from the kernel.

So we have a few questions:

• Are we missing a functionality in that regard?
• If Yes, where?
• If No, is this something considered in the roadmap?

Thanks for the feedback!

[markwallace-microsoft]

Hi @markbartolocodit
what exception are you seeing? Also can you provide some sample code and a stack trace for the issue. Thanks!

[markbartolocodit]

Semantic Kernel is being initialised in an ASP.NET Core App as folllows:

 var kernel = Kernel.CreateBuilder()
        .AddAzureOpenAIChatCompletion(
          myConfig.KernelMemory.DefaultOverrides.ChatModelDeployment,
          myConfig.KernelMemory.Services.OpenAIService.Endpoint,
          myConfig.KernelMemory.Services.OpenAIService.ApiKey
        )
        .Build();

The code that is using the semantic kernel in a Controller is the following:

Microsoft.SemanticKernel.Kernel kernel;
...
KernelFunction? myFunction = kernel.CreateFunctionFromPrompt(finalPrompt);
FunctionResult? result = await myFunction.InvokeAsync(kernel, arguments).ConfigureAwait(false); 

The exception is occuring in myFunction.InvokeAsync

In AppInsights I'm seeing:

There is no way to interfere to see any exception happening from within the Kernel.

The main goal would be for the 429 to bubble up in the myFunction.InvokeAsync.

[markwallace-microsoft]

Hi @markbartolocodit
I created a unit test to check this behaviour, take a look here: https://github.com/microsoft/semantic-kernel/pull/9772/files

Based on this you should be able to catch a HttpOperationException. Let me know if this doesn't work for you.

[dmytrostruk]

@markbartolocodit If you have ASP.NET Core app, you are invoking Kernel in Controller and you don't see an exception, make sure that you don't have global filter/middleware in your app that intercepts the exception automatically. If you want to catch 429 exceptions in controller, you need to make sure that global exception handling doesn't include 429 error.