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
[Profiling] Ignore error frames #176537
[Profiling] Ignore error frames #176537
Conversation
This change allows the Universal Profiling agent to send error frames, which will give us more accurate values for CO2 emission and $ costs. The reason is that unwinding errors resulting in 0-length stacktraces happen quite often. These are not sent to the backend currently, so the related CPU activity doesn't go into the calculations. This can make up showing 10% less CPU / CO2 / costs in the UI. Adding artificial error frames in case of unwinding errors guarantees that stacktraces always have a length of > 0. Once we settled on how error frames can be displayed in a user-friendly way, this code can be removed.
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
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.
Core changes LGTM
…to ignore-error-frames
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
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Public APIs missing comments
Async chunks
Page load bundle
Unknown metric groupsAPI count
ESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @rockdaboot |
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
This change allows the Universal Profiling agent to send error frames, which will give us more accurate values for CO2 emission and $ costs. The reason is that unwinding errors resulting in 0-length stacktraces happen quite often. These are not sent to the backend currently, so the related CPU activity doesn't go into the calculations. This can make up showing 10% less CPU / CO2 / costs in the UI. Adding artificial error frames in case of unwinding errors guarantees that stacktraces always have a length of > 0. Once we settled on how error frames can be displayed in a user-friendly way, this code can be removed. --------- Co-authored-by: Joel Höner <joel@elastic.co> Co-authored-by: Caue Marcondes <caue.marcondes@elastic.co>
This change allows the Universal Profiling agent to send error frames, which will give us more accurate values for CO2 emission and $ costs. The reason is that unwinding errors resulting in 0-length stacktraces happen quite often. These are not sent to the backend currently, so the related CPU activity doesn't go into the calculations. This can make up showing 10% less CPU / CO2 / costs in the UI. Adding artificial error frames in case of unwinding errors guarantees that stacktraces always have a length of > 0. Once we settled on how error frames can be displayed in a user-friendly way, this code can be removed. --------- Co-authored-by: Joel Höner <joel@elastic.co> Co-authored-by: Caue Marcondes <caue.marcondes@elastic.co>
This change allows the Universal Profiling agent to send error frames, which will give us more accurate values for CO2 emission and $ costs. The reason is that unwinding errors resulting in 0-length stacktraces happen quite often. These are not sent to the backend currently, so the related CPU activity doesn't go into the calculations. This can make up showing 10% less CPU / CO2 / costs in the UI. Adding artificial error frames in case of unwinding errors guarantees that stacktraces always have a length of > 0. Once we settled on how error frames can be displayed in a user-friendly way, this code can be removed. --------- Co-authored-by: Joel Höner <joel@elastic.co> Co-authored-by: Caue Marcondes <caue.marcondes@elastic.co>
This change allows the Universal Profiling agent to send error frames, which will give us more accurate values for CO2 emission and $ costs.
The reason is that unwinding errors resulting in 0-length stacktraces happen quite often. These are not sent to the backend currently, so the related CPU activity doesn't go into the calculations. This can make up showing 10% less CPU / CO2 / costs in the UI.
Adding artificial error frames in case of unwinding errors guarantees that stacktraces always have a length of > 0.
Once we settled on how error frames can be displayed in a user-friendly way, this code can be removed.