-
Notifications
You must be signed in to change notification settings - Fork 332
Add Retryable/Non-Retryable Exception + API Calls Metrics for O365 #6238
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
a89b3d7
Add Retryable/Non-Retryable Exception + API Calls Metrics for O365
59d4462
Add Retryable/Non-Retryable Exception + API Calls Metrics for O365
f06a9e5
Merge branch 'opensearch-project:main' into main
zeligsonbrett a48f952
Add Retryable/Non-Retryable Exception + API Calls Metrics for O365
2c50d6e
Address typo and improve publishErrorTypeMetricCounter function (#6253)
vecheka 2420ad6
Address typo and improve publishErrorTypeMetricCounter function (#6253)
vecheka 6c5ed31
Merge remote-tracking branch 'upstream/main'
a32435c
Merge branch 'main' into main
zeligsonbrett File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing to increase the retryable error counter here? Simply calling
handleExceptionMetricsmethod from here without this if else checking would be better.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this is throwing a RuntimeException, it will get caught in the outer catch which contains the handleExceptionMetrics(e) call.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No. It doesn't work that way, since you are throwing a RuntimeException. It won't be an instance of Office365 exception
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, but from my understanding when the RuntimeException is thrown from within this if statement, it would get caught in the outer catch which contains the handleExceptionMetrics() call which would increment the retryableErrorsCounter within handleExceptionMetrics() because the caught error would be a RuntimeException (not an Office365Exception anymore) as you said.