feat: Crash report content optimization #294
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
rb-union
reviewed
Apr 29, 2024
|
[是否满足兼容性要求] Y |
Crash report content optimization 1.add key of coredumpListCount: Record the number of query results for the ‘sudo coredumpctl list’ command; 2.add key of repeatCoredumps: Record the number of times crash information appears in different time ranges from the last reported time node to the current time node; 3.Definition of high-frequency crash application: The number of crashes accounts for more than 80% of the total number of newly added crashes, or occurs more than 3 times repeatedly; 4.Add the coredumpReportMax(default to 50) parameter configuration in Dconfig/Gsettings to limit the maximum number of entries per report; 6.About coredump detail infos, such as maps info, only report the first 200 rows; 7.Analyze the business code of crash details information and trigger it when adjusting to the ready burial point. Log: Crash report content optimization Task: Technical special project-10320240422
deepin pr auto reviewMake the log viewer applet more powerful, can execute the command of the system and get the result. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: starhcq, wyu71 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
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.
Crash report content optimization
1.add key of coredumpListCount: Record the number of query results for the ‘sudo coredumpctl list’ command;
2.add key of repeatCoredumps: Record the number of times crash information appears in different time ranges from the last reported time node to the current time node;
3.Definition of high-frequency crash application: The number of crashes accounts for more than 80% of the total number of newly added crashes, or occurs more than 3 times repeatedly;
4.Add the coredumpReportMax(default to 50) parameter configuration in Dconfig/Gsettings to limit the maximum number of entries per report;
6.About coredump detail infos, such as maps info, only report the first 200 rows;
7.Analyze the business code of crash details information and trigger it when adjusting to the ready burial point.
Log: Crash report content optimization
Task: https://pms.uniontech.com/task-view-343581.html