Skip to content
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

Conversation

achyutjhunjhunwala
Copy link
Contributor

@achyutjhunjhunwala achyutjhunjhunwala commented Jun 17, 2024

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

  • Add Locator for Dataset Quality Page
  • Add tests

Demo

Jul-04-2024 15-54-22

@achyutjhunjhunwala achyutjhunjhunwala added release_note:skip Skip the PR/issue when compiling release notes Team:obs-ux-logs Observability Logs User Experience Team labels Jun 17, 2024
@achyutjhunjhunwala achyutjhunjhunwala self-assigned this Jun 17, 2024
@obltmachine
Copy link

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • /oblt-deploy : Deploy a Kibana instance using the Observability test environments.
  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

@achyutjhunjhunwala
Copy link
Contributor Author

/ci

@achyutjhunjhunwala
Copy link
Contributor Author

/ci

@achyutjhunjhunwala
Copy link
Contributor Author

/ci

@achyutjhunjhunwala
Copy link
Contributor Author

/ci

@kibana-ci
Copy link
Collaborator

kibana-ci commented Jun 20, 2024

💔 Build Failed

Failed CI Steps

History

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @achyutjhunjhunwala

achyutjhunjhunwala added a commit that referenced this pull request Jul 4, 2024
… 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.
@achyutjhunjhunwala
Copy link
Contributor Author

/ci

@achyutjhunjhunwala achyutjhunjhunwala marked this pull request as ready for review July 4, 2024 13:46
@achyutjhunjhunwala achyutjhunjhunwala requested review from a team as code owners July 4, 2024 13:46
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

@botelastic botelastic bot added the ci:project-deploy-observability Create an Observability project label Jul 4, 2024
Comment on lines 35 to 38
"@kbn/core-notifications-browser",
"@kbn/deeplinks-observability",
"@kbn/router-utils",
"@kbn/share-plugin"
Copy link
Member

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

Copy link
Contributor Author

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kertal The linter keeps on adding it back

347aded

Copy link
Member

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 :)

Copy link
Contributor

@yngrdyn yngrdyn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@elasticmachine
Copy link
Contributor

elasticmachine commented Jul 8, 2024

⏳ Build in-progress

History

cc @achyutjhunjhunwala

Copy link
Member

@kertal kertal left a 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

@achyutjhunjhunwala achyutjhunjhunwala merged commit 2e8ca07 into elastic:main Jul 9, 2024
22 checks passed
@achyutjhunjhunwala achyutjhunjhunwala deleted the Add-quality-issues-table-to-Logs-Flyout branch July 9, 2024 10:27
@kibanamachine kibanamachine added v8.16.0 backport:skip This commit does not require backporting labels Jul 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:skip This commit does not require backporting ci:project-deploy-observability Create an Observability project release_note:skip Skip the PR/issue when compiling release notes Team:obs-ux-logs Observability Logs User Experience Team v8.16.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants