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

.Net: Added example with telemetry in Filters #6943

Merged
merged 8 commits into from
Jun 25, 2024

Conversation

dmytrostruk
Copy link
Member

Motivation and Context

Related: #5436

Kernel and connectors have out-of-the-box telemetry to capture key information, which is available during requests.
In most cases this telemetry should be enough to understand how the application behaves.
This example contains the same telemetry recreated using Filters.
This should allow to extend existing telemetry if needed with additional information and have the same set of logging messages for custom connectors.

Contribution Checklist

@dmytrostruk dmytrostruk self-assigned this Jun 25, 2024
@dmytrostruk dmytrostruk requested a review from a team as a code owner June 25, 2024 00:28
@markwallace-microsoft markwallace-microsoft added .NET Issue or Pull requests regarding .NET code documentation labels Jun 25, 2024
@dmytrostruk dmytrostruk added this pull request to the merge queue Jun 25, 2024
@dmytrostruk dmytrostruk removed this pull request from the merge queue due to a manual request Jun 25, 2024
@dmytrostruk dmytrostruk enabled auto-merge June 25, 2024 16:08
@dmytrostruk dmytrostruk added this pull request to the merge queue Jun 25, 2024
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jun 25, 2024
@dmytrostruk dmytrostruk added this pull request to the merge queue Jun 25, 2024
Merged via the queue into microsoft:main with commit b89722d Jun 25, 2024
15 checks passed
@dmytrostruk dmytrostruk deleted the telemetry-with-filters branch June 25, 2024 17:46
LudoCorporateShark pushed a commit to LudoCorporateShark/semantic-kernel that referenced this pull request Aug 25, 2024
### Motivation and Context

<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->

Related: microsoft#5436

Kernel and connectors have out-of-the-box telemetry to capture key
information, which is available during requests.
In most cases this telemetry should be enough to understand how the
application behaves.
This example contains the same telemetry recreated using Filters.
This should allow to extend existing telemetry if needed with additional
information and have the same set of logging messages for custom
connectors.

### Contribution Checklist

<!-- Before submitting this PR, please make sure: -->

- [x] The code builds clean without any errors or warnings
- [x] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [x] All unit tests pass, and I have added new tests where possible
- [x] I didn't break anyone 😄
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation .NET Issue or Pull requests regarding .NET code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants