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

feat(chat): Report docs fallback telemetry #825

Merged
merged 1 commit into from
Sep 23, 2024

Conversation

nirinchev
Copy link
Contributor

Description

Related to VSCODE-605 and VSCODE-570 - reports docs chatbot error in case we need to fallback to copilot model for docs responses. Currently doesn't report the error message as I wasn't sure if that could contain some PII or other data we don't want stored in a 3rd party provider. In case we notice a significant amount of chatbot errors, we can iterate on the reporting mechanism to also include diagnostic information.

Checklist

Motivation and Context

  • Bugfix
  • New feature
  • Dependency update
  • Misc

Open Questions

Dependents

Types of changes

  • Backport Needed
  • Patch (non-breaking change which fixes an issue)
  • Minor (non-breaking change which adds functionality)
  • Major (fix or feature that would cause existing functionality to change)

@@ -399,13 +399,6 @@ suite('Participant Controller Test Suite', function () {
TelemetryEventTypes.PARTICIPANT_WELCOME_SHOWN
);
expect(telemetryTrackStub.lastCall.args[1]).to.be.undefined;

telemetryTrackStub
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This must have been a bad merge that I didn't notice.

@nirinchev nirinchev merged commit 5e0a09d into VSCODE-528-mongodb-copilot Sep 23, 2024
3 checks passed
@nirinchev nirinchev deleted the ni/docs-fallback-telemetry branch September 23, 2024 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants