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

Triage Crawler exceptions: BadRequest StorageErrors #10

Open
brphelps opened this issue Mar 12, 2020 · 2 comments
Open

Triage Crawler exceptions: BadRequest StorageErrors #10

brphelps opened this issue Mar 12, 2020 · 2 comments
Assignees

Comments

@brphelps
Copy link
Contributor

exceptions
| summarize
BadRequestStorageError = countif(outerMessage contains "Bad Request" and outerMessage contains "StorageError")

@brphelps
Copy link
Contributor Author

When triaging, make sure to identify whether this issue should or shouldn't be happening -- if it's not truly exceptional, try to convert to a less interesting tracing method (e.g. a warning trace).

@jcfiorenzano jcfiorenzano self-assigned this Mar 13, 2020
@jcfiorenzano
Copy link
Contributor

Is really difficult to determine where is this bug originated, the exceptions does not have an operation_id so I couldn't find a request that failed.

by looking at the code I am assuming that this is happening in the method upset of the attachmentStore file that have something like
image
so if the token has some invalid characters we could have this problem.

More investigation and better logging is going to be needed in order to prove identify the issue

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

No branches or pull requests

2 participants