Log ingestion error on 206 response #2065
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
if you hide whitespace in the diff it will help |
heyams
reviewed
Jan 22, 2022
...c/main/java/com/microsoft/applicationinsights/agent/internal/telemetry/TelemetryChannel.java
Show resolved
Hide resolved
| case 408: // REQUEST TIMEOUT | ||
| case 500: // INTERNAL SERVER ERROR | ||
| case 503: // SERVICE UNAVAILABLE | ||
| case 429: // TOO MANY REQUESTS | ||
| // TODO (heya) should we write to disk on any of these response codes? |
There was a problem hiding this comment.
not sure... if we don't write to disk, we should consider tracking how many requests we drop. Let's think about it.. need to come up with new property in customdimension.. it can be part of network statsbeat..
There was a problem hiding this comment.
can you update the todo to track data drop via statsbeat?
...c/main/java/com/microsoft/applicationinsights/agent/internal/telemetry/TelemetryChannel.java
Show resolved
Hide resolved
trask
changed the title
heyams
approved these changes
Jan 24, 2022
trask
commented
Jan 24, 2022
Comment on lines
+305
to
+314
| case 408: // REQUEST TIMEOUT | ||
| case 429: // TOO MANY REQUESTS | ||
| case 500: // INTERNAL SERVER ERROR | ||
| case 503: // SERVICE UNAVAILABLE | ||
| operationLogger.recordFailure( | ||
| "received response code " | ||
| + statusCode | ||
| + " (telemetry will be stored to disk and retried later)"); | ||
| onFailure.accept(true); | ||
| break; |
There was a problem hiding this comment.
this is the list of response codes that 2.x used to retry on, I think it's a good list, not sure when we diverged from it
heyams
reviewed
Jan 25, 2022
...est/java/com/microsoft/applicationinsights/agent/internal/localstorage/IntegrationTests.java
Outdated
Show resolved
Hide resolved
heyams
approved these changes
Jan 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #2064, which we never noticed since we didn't log it.
Now the error in #2064 would be logged as: