Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

C# Kernel: Add End-to-End Telemetry #1651

Closed
5 tasks done
evchaki opened this issue Jun 21, 2023 · 2 comments · Fixed by #1905
Closed
5 tasks done

C# Kernel: Add End-to-End Telemetry #1651

evchaki opened this issue Jun 21, 2023 · 2 comments · Fixed by #1905
Assignees
Labels
kernel Issues or pull requests impacting the core kernel .NET Issue or Pull requests regarding .NET code sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Milestone

Comments

@evchaki
Copy link
Contributor

evchaki commented Jun 21, 2023

Leverage ILogger with Azure Monitor (AppInsights) to send custom telemetry for the following:

  1. Ask (disabled by default) – the actual Ask (text) coming into the Kernel from the application (example: “Create an email to my boss with a summarization of this ......” this will be important in Dev and maybe UAT/test environments. But for PII in production it should be disabled

  2. Planner (enabled by default) – this is the planner step (either using one of our planners or if the developer hard coded in a plan
    a. Ideal information to store here: Execution time, Model used for planner, success state (Success / Failed), Plan returned, total tokens used

  3. Steps executed for the returned plan (enabled by default)
    a. Ideal information to store here: Plugin executed, execution time, success state (Success / Failed), Tokens used, Model used, Plan this was run from

  4. Kernel Errors throughout the process
    a. Critical, Failures, Warnings – (enabled by default)
    b. Non-fatal (disabled by default)

Tasks

Preview Give feedback
@evchaki evchaki added enhancement .NET Issue or Pull requests regarding .NET code kernel Issues or pull requests impacting the core kernel labels Jun 21, 2023
@evchaki evchaki added this to the Sprint 34 milestone Jun 21, 2023
@evchaki evchaki added the sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community) label Jun 21, 2023
@evchaki evchaki moved this to Sprint: Planned in Semantic Kernel Jun 21, 2023
@dmytrostruk dmytrostruk moved this from Sprint: Planned to Sprint: In Progress in Semantic Kernel Jun 22, 2023
@evchaki evchaki moved this from Sprint: In Progress to Sprint: Planned in Semantic Kernel Jun 22, 2023
@dmytrostruk dmytrostruk moved this from Sprint: Planned to Sprint: In Progress in Semantic Kernel Jun 26, 2023
@dmytrostruk dmytrostruk linked a pull request Jul 8, 2023 that will close this issue
5 tasks
@dmytrostruk
Copy link
Member

Telemetry for Kernel errors will be handled after exception handling issue is closed: #1669

@dmytrostruk dmytrostruk moved this from Sprint: In Progress to Sprint: In Review in Semantic Kernel Jul 8, 2023
@github-project-automation github-project-automation bot moved this from Sprint: In Review to Sprint: Done in Semantic Kernel Jul 18, 2023
@alexminza
Copy link

LangSmith is a great tool that builds on top of this type of functionality #2070

@lemillermicrosoft lemillermicrosoft modified the milestones: Sprint 34, v1 Sep 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kernel Issues or pull requests impacting the core kernel .NET Issue or Pull requests regarding .NET code sk team issue A tag to denote issues that where created by the Semantic Kernel team (i.e., not the community)
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

4 participants