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.

Sign up for GitHub

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

Jump to bottom

Cosmos SDK "failures" in app insights - "The operation was aborted" #29574

Open
timtucker-dte opened this issue May 3, 2024 · 1 comment
Open

Cosmos SDK "failures" in app insights - "The operation was aborted" #29574

timtucker-dte opened this issue May 3, 2024 · 1 comment
Assignees
@sajeetharan
Labels
Client This issue points to a problem in the data-plane of the library. Cosmos customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@timtucker-dte
Copy link

Seeing repeated dependency calls to Cosmos showing up as "failed" in app insights with a result code of 0 and an error of "The operation was aborted".

Seems to happen on POST requests.

Doesn't seem to trigger any exceptions from the SDK, so presumably this is something that's happening internally.

What causes this?

Is it something as basic as determining whether or not to use a query plan? Something else?

Looking to cut down on noise in logs:

  • If there anything on our side that can cut down on the # of calls?
  • If not, is there a combination of criteria that we should be filtering on in our telemetry processor to flag these as success? (presumably there could be other operation aborted errors within the SDK that might be actual errors)
@github-actions github-actions bot added Client This issue points to a problem in the data-plane of the library. Cosmos customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team. labels May 3, 2024
@github-actions GitHub Actions
Copy link

github-actions bot commented May 3, 2024

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @sajeetharan @simorenoh @v1k1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sajeetharan sajeetharan

Labels
Client This issue points to a problem in the data-plane of the library. Cosmos customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sajeetharan @timtucker-dte