-
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
[Synthetics] Waterfall view #84821
[Synthetics] Waterfall view #84821
Conversation
e94dfaf
to
091f610
Compare
091f610
to
a06bfb1
Compare
Pinging @elastic/uptime (Team:uptime) |
@elasticmachine merge upstream |
return ( | ||
<EuiLink> | ||
<Link data-test-subj={`step-detail-link`} to={to}> | ||
{children} | ||
</Link> | ||
</EuiLink> | ||
); |
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 kills the purpose of EuiLink, we have a small utility for these kind of use cases,
can you please use that https://github.com/elastic/kibana/blob/master/x-pack/plugins/uptime/public/components/common/react_router_helpers/link_for_eui.tsx#L55
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.
Sure, I can change it. I'd actually copied this style from here: https://github.com/elastic/kibana/blob/master/x-pack/plugins/uptime/public/components/common/monitor_page_link.tsx#L22, so maybe that needs changing too?
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.
yeah we should change it there as well. i guess we can create a follow up issue to refactor all places in uptime.
x-pack/plugins/uptime/public/components/monitor/synthetics/executed_step.tsx
Show resolved
Hide resolved
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.
Looks great, code wise look ok. Just need to figure out the timing stuff and why some events are missing. I am open to getting those resolved in agent or wait for those to be get fixed.
Thanks for the review. I'll be switching the UI code over to use @vigneshshanmugam fix from the Agent side for the timings. I'm not sure what's happening on the missing events front though. |
^ We spoke on Zoom and the above was an outdated Agent version so the new |
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.
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Distributable file count
History
To update your PR or re-run it, just comment with: |
* Add a new synthetics step detail page for displaying waterfall data
Summary
This PR implements the majority of #80162, #80168 (note: the popover is yet to come, I had missed this on the ticket, but don't want to hold up this PR), and #80170.
Notes
There is a new API for retrieving network events.
The journey API has been slightly extended to return a
details
object along with thesteps
, this contains details on the timestamp of the run, and next / previous run details. Whilst this information isn't used directly where we list the steps yet, the refactors that are due in the future should yield this a useful addition there too. Regardless, the performance impact shouldn't be large here.Filtering will follow (if there's time before FF)
Testing