-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[SLO][Embeddable] Fix Kibana reporting screenshot issue #169929
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
Pinging @elastic/actionable-observability (Team: Actionable Observability) |
bad3931
to
44ff9aa
Compare
this.node = node; | ||
// required for the export feature to work | ||
this.node.setAttribute('data-shared-item', ''); |
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.
This is needed according to this. Otherwise reporting wouldn't work
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.
Just a concern about calling the callback without a useEffect, but we need to validate my assumption before
if (!isLoading) { | ||
onRenderComplete(); | ||
} |
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.
🤔 I wonder if this is not triggered at every rerender? One way to check would be to console log something here.
95fd0ca
to
460f050
Compare
460f050
to
01dcbcc
Compare
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.
👍🏻 Thanks for the change
@elasticmachine merge upstream |
c9c9fd8
to
e2ba41e
Compare
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: cc @mgiota |
Resolves elastic#169716 ## 🍒 Summary The reporting plugin waits for a renderComplete signal when the embeddable has finished loading any data and is correctly rendered so the headless Chromium can take a screenshot. This PR calls the RenderCompleteDispatcher on the SLO Overview embeddable when all the child components have finished loading. https://elastic.slack.com/archives/CFFQ7RP9B/p1614267987040400 ## How to test - Add an SLO panel to the dashboard - click on share -> PDF reports > Generate PDF on the top right navigation bar - No Timeout error should appear on the generated PDF <img width="1407" alt="Screenshot 2023-10-26 at 15 05 05" src="https://github.com/elastic/kibana/assets/2852703/45c2c868-edbe-426e-bc05-5794c2bfa91e"> --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Pinging @elastic/obs-ux-management-team (Team:obs-ux-management) |
Resolves #169716
🍒 Summary
The reporting plugin waits for a renderComplete signal when the embeddable has finished loading any data and is correctly rendered so the headless Chromium can take a screenshot. This PR calls the RenderCompleteDispatcher on the SLO Overview embeddable when all the child components have finished loading.
https://elastic.slack.com/archives/CFFQ7RP9B/p1614267987040400
How to test