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

[botbuilder-dialogs] Waterfall dialogs do not log telemetry on reason===replaceCalled #6381

Open
alexrecuenco opened this issue Sep 17, 2021 · 8 comments
Labels
Bot Services Required for internal Azure reporting. Do not remove. Do not change color. customer-replied-to Indicates that the team has replied to the issue reported by the customer. Do not delete. customer-reported Issue is created by anyone that is not a collaborator in the repository. feature-request A request for new functionality or an enhancement to an existing one. needs-triage The issue has just been created and it has not been reviewed by the team. P1 Painful if we don't fix, won't block releasing
Milestone

Comments

@alexrecuenco
Copy link

Versions

  • Botbuilder version 4.1.6
  • Node version 14.16.1

Describe the bug

Telemetry is not logged if a waterfall dialog ends with replaceCalled, instead of endCalled or cancelCalled.

To Reproduce

Steps to reproduce the behavior:

  1. Start dialog with a console log telemetry
  2. End dialog with replace called
  3. End dialog will not get logged

Expected behavior

When a dialog ends through replaceCalled, telemetry should be logged.

Additional context

I imagine this is a slight oversight in the endDialog method of waterfallDialog, but it might've been done on purpose, in which case, I am sorry.

@srinaath
Copy link

@alexrecuenco This seems to be a really old version of botbuilder-js (3 years ago). This repo has undergone massive upgrades since then and the bug could be resolved in the latest version. Is there a reason for you to not upgrade to 4.14.0?

@joshgummersall

@alexrecuenco
Copy link
Author

@srinaath
Sorry, this is currently an issue on the main branch. https://github.com/microsoft/botbuilder-js/blob/b1d137f86aa2beb0642e85ed3398d147dd5c7d0e/libraries/botbuilder-dialogs/src/waterfallDialog.ts#L296

I put as version number the number on the package.json on the folder of botbuilder-dialogs, which I now realize was incorrect

@joshgummersall
Copy link

@alexrecuenco we maintain parity with the .NET SDK, which has the same behavior. I'll transfer this issue to the SDK repo where it'll get some visibility. I suspect this was an intentional design decision though and is not a bug.

@joshgummersall joshgummersall transferred this issue from microsoft/botbuilder-js Sep 17, 2021
@joshgummersall joshgummersall removed their assignment Sep 17, 2021
@joshgummersall joshgummersall added the customer-reported Issue is created by anyone that is not a collaborator in the repository. label Sep 17, 2021
@stevkan stevkan added Bot Services Required for internal Azure reporting. Do not remove. Do not change color. customer-replied-to Indicates that the team has replied to the issue reported by the customer. Do not delete. labels Sep 20, 2021
@lauren-mills
Copy link

@mrivera-ms - Could you comment on whether this behavior is a bug or by design?

@alexrecuenco
Copy link
Author

It has been some time, any updates?

@gabog gabog assigned gabog and unassigned mrivera-ms Dec 14, 2021
@tdurnford
Copy link
Contributor

@gabog Do you have any updates on this issue?

@carlosscastro
Copy link
Member

@gabog can we assign a release for this issue or prioritize according to its urgency? Thanks

@gabog gabog removed their assignment Jan 24, 2022
@gabog gabog added the feature-request A request for new functionality or an enhancement to an existing one. label Jan 24, 2022
@gabog gabog added this to the R16 milestone Jan 24, 2022
@gabog gabog added needs-triage The issue has just been created and it has not been reviewed by the team. P1 Painful if we don't fix, won't block releasing labels Jan 24, 2022
@gabog
Copy link
Contributor

gabog commented Jan 24, 2022

I added the the feature request to our backlog, as a workaround, you can override the method and log the event until this is added to the SDK

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bot Services Required for internal Azure reporting. Do not remove. Do not change color. customer-replied-to Indicates that the team has replied to the issue reported by the customer. Do not delete. customer-reported Issue is created by anyone that is not a collaborator in the repository. feature-request A request for new functionality or an enhancement to an existing one. needs-triage The issue has just been created and it has not been reviewed by the team. P1 Painful if we don't fix, won't block releasing
Projects
None yet
Development

No branches or pull requests

10 participants