Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
|
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
997721d to
0ab9dda
Compare
8368ce0 to
513ab04
Compare
|
@simianhacker I enabled slo on serverless and made it appear in the navigation as well. Let me know if it looks fine |
|
@CoenWarmer Thanks for fixing the redirect issue. How about redirecting to old slo detail page? This will not work
Update: I can update the SimpleRedirect function to read the url and extract the slo id. Then I can use the extracted id to construct the path in the navigateToApp method call. I was just wondering if there is something out of the box. |
simianhacker
left a comment
There was a problem hiding this comment.
LGTM! Good Job!
I filed an issue for the search bar, I noticed it while reviewing your change but then check it was broken on main: #178771
|
@simianhacker I already have a fix for the issue you created. #178582. |
Dosant
left a comment
There was a problem hiding this comment.
x-pack/plugins/serverless_observability/public/navigation_tree.ts lgtm
sebelga
left a comment
There was a problem hiding this comment.
Changes to observability navigation_tree.ts LGTM 👍
|
@elasticmachine merge upstream |
|
@CoenWarmer regarding handling redirection of the old slo detail and edit pages, here's what I've done and works fine. If you know any other better out of the box solution, just let me know Screen.Recording.2024-03-18.at.13.30.38.mov |
| }, | ||
| [OLD_SLO_DETAIL_PATH]: { | ||
| handler: () => { | ||
| return <SimpleRedirect to="/:sloId" redirectToApp="slo" />; |
There was a problem hiding this comment.
Don't you need something before /:sloId? How does the <SimpleRedirect /> component distinguish between the edit and detail route? The to prop is the same in both cases?
There was a problem hiding this comment.
@CoenWarmer I handle both edit and detail routes in this condition, which takes out the /slos part from the url and keeps /edit/1234 or /1234 accordingly:
if (to === '/:sloId') {
to = pathname.split('/slos')[1];
}
Initially I added this condition just for the detail path, but then it worked out well for the edit as well. What do you think? I agree not the most elegant way. I am wondering if React router has something out of the box, that you are aware of.
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
|
@elasticmachine merge upstream |
dominiqueclarke
left a comment
There was a problem hiding this comment.
Smoke tests LGTM
|
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsTest Failures
Metrics [docs]Module Count
Public APIs missing comments
Async chunks
Public APIs missing exports
Page load bundle
Unknown metric groupsAPI count
async chunk count
ESLint disabled in files
ESLint disabled line counts
miscellaneous assets size
References to deprecated APIs
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: cc @mgiota |
Fixes #176420
🍒 Summary
This PR copies the SLO code that was inside the Observability app into its own app under
observability-solution/slofolder.Screen.Recording.2024-03-09.at.00.45.40.mov
✔️ Acceptance criteria
app/slosx-pack/plugins/observability_solution/slo.observability_solution/observabilitycode has been removed. A new clean up round might be needed though for possible leftovers.ApplicationUsageTrackingProviderwhich will send sloApplication usageinformation tracked by thesloappIdapp/observability/slosroute toapp/slosxpack.observability.slokeys toxpack.sloin the translation files🌮 How to test
Design and functionality didn't change, so simply navigate to existing slo pages and try to break it
TODO