Azure Bot Service does not provide error details for anything but HTTP errors
Nobody has claimed this yet.
- Dominant language
- TypeSpec
- Stars
- 1.1k
- Forks
- 340
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 12
Description
Azure Bot Service logs for the Web Chat channel only provides error details when the error revolves around the actual HTTP connection itself.
Errors that are outside of the HTTP protocol (i.e. "Operating System", or whatever the equivalent of an OS is for the Azure Bot Service) are not being reported in the error details in the "Health Status" history
E.g.
- Provide a Message Endpoint URL that contains a DNS name that cannot be resolved via DNS
Expected Result:
- Error Detail should say: No such hostname
Actual Result:
- Error Detail is empty. Only "There was an error sending this message to your bot" is displayed.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by reproducing the Web Chat Health Status failure with a DNS-unresolvable Message Endpoint URL, then trace where the error detail is produced. Done means the history shows a specific detail such as “No such hostname” instead of an empty detail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100