-
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
[Logs Explorer] Add logic to render degraded fields table in Logs Flyout #186287
[Logs Explorer] Add logic to render degraded fields table in Logs Flyout #186287
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
/ci |
/ci |
/ci |
/ci |
💔 Build FailedFailed CI StepsHistory
To update your PR or re-run it, just comment with: |
… main DQ Page page (#187450) ## Summary This PR is a prerequisite to the Locator Implementation for Logs Explorer - #186287 ## Problem Statement - Integrations were fetched when the main DQ page loads and stored in the State Machine. This means when the Flyout Opens, it was referencing already fetched data from the main page, updating the URL and then that was used to render certain sections on the Flyout. This causes issues as when a Locator is used to directly open the Flyout from some other page. In that case everything happen asynchronously causing the data to be not present when the flyout open thus those integration sections were not present. ## Solution - Now when the flyout is opened or is already open, it reads the basic params from the URL like `DataStream`. With this information, it make API call to fetch Integration information and thus making it independent. - Does this means you duplicated the Logic to fetch Integrations ? Yes and No. Logic has to be duplicated as Flyout is moving to its own page very soon. This means it would anyhow not be able to re-use that Integration Information available. Secondly the duplication is not one to one, its more catered towards Flyout logic - Split the state machine to make Integration Calls only when the opened Dataset is actually an integration. This is done by chaining the respective states after the `DataStreamSettings` state confirms presence of Integration. ## What else has been done - Type cleaning: A lot of types has to be refactored to make this change. Also simplified some duplicate types. We were using - Runtime types - Types Derived from Runtime Types - Inferred Types from API Responses We don't need the 3rd one. 1 and 2 and sufficient.
/ci |
Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs) |
"@kbn/core-notifications-browser", | ||
"@kbn/deeplinks-observability", | ||
"@kbn/router-utils", | ||
"@kbn/share-plugin" |
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.
QQ: just looked at the code we own, it seems there's just the share plugin being added, why are
"@kbn/deeplinks-observability",
"@kbn/router-utils"
required? thx
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.
That's actually a very good question.
@kbn/deeplinks-observability
is being imported here
But i couldn't myself find why "@kbn/router-utils"
got added. I thought job would have added it. But looks like not. I will remove this
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.
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.
Alright, linter knows it best :)
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 in-progress
History
|
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.
Code owned by DataDiscovery LGTM, it's just the addon of the share plugin to the unified_doc_viewer. Didn't test
Summary
Closes - #172272
The PR adds the degraded Field Table in the Logs Flyout. The accordion is kept closed by default. For demo purposes below screenshot will show it expanded
This PR will also fix a very simply Flaky Test - #186244
Pending Items
Demo