-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
[chore](log) Standardize S3 failure log formats to enable critical operation monitoring #49813
Conversation
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
run buildall |
TPC-H: Total hot run time: 35451 ms
|
TPC-DS: Total hot run time: 192496 ms
|
ClickBench: Total hot run time: 31.06 s
|
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
…eration monitoring This change unifies S3 error logging patterns for four critical operations that require alerting: * failed to complete multipart upload * failed to upload part * failed to put object * failed to get object.*\.(dat|idx) (specific to data/index files)
67a9d5f
to
c4a98da
Compare
run buildall |
TPC-H: Total hot run time: 34158 ms
|
TPC-DS: Total hot run time: 193916 ms
|
ClickBench: Total hot run time: 30.89 s
|
BE UT Coverage ReportIncrement line coverage Increment coverage report
|
PR approved by anyone and no changes requested. |
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.
LGTM
PR approved by at least one committer and no changes requested. |
…eration monitoring (#49813) This change unifies S3 error logging patterns for four critical operations that require alerting: * failed to complete multipart upload * failed to upload part * failed to put object * failed to get object.*\.(dat|idx) (specific to data/index files)
What problem does this PR solve?
This change unifies S3 error logging patterns for four critical operations that require alerting:
Release note
None
Check List (For Author)
Test
Behavior changed:
Does this need documentation?
Check List (For Reviewer who merge this PR)