-
Notifications
You must be signed in to change notification settings - Fork 8.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[8.x] [Dataset Quality] Implement _ignored root cause identification …
…flow (#192370) (#194910) # Backport This will backport the following commits from `main` to `8.x`: - [[Dataset Quality] Implement _ignored root cause identification flow (#192370)](#192370) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Achyut Jhunjhunwala","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-10-04T07:41:55Z","message":"[Dataset Quality] Implement _ignored root cause identification flow (#192370)\n\n## Summary\r\n\r\nCloses - https://github.com/elastic/kibana/issues/192471\r\nCloses - https://github.com/elastic/kibana/issues/191055\r\n\r\nThe PR adds Flyout to the Degraded Fields inside the Dataset Quality\r\nDetails page where the Root Cause of the Degraded Field is diagnosed.\r\n\r\n## Pending Items\r\n\r\n- [x] API Tests for 1 new and 2 old API modifications\r\n- [x] E2E Tests for the Flyout\r\n\r\n## How to test this\r\n\r\nNOTE (Below guide is for Stateful, you can do the same for serverless)\r\n\r\n- Checkout the PR using - `gh pr checkout 192370`\r\n\r\n1. Start the FTR server using the command below\r\n\r\n```\r\n yarn test:ftr:server --config ./x-pack/test/functional/apps/dataset_quality/config.ts\r\n ```\r\n \r\n 2. Go to the following path - `x-pack/test/functional/apps/dataset_quality/degraded_field_flyout.ts`\r\n 3. Comment out the 2 `after` blocks present at Line - 54-56 and 414-416\r\n 4. Run the FTR runner using the command below\r\n \r\n ```\r\nyarn test:ftr:runner --config ./x-pack/test/functional/apps/dataset_quality/config.ts --include ./x-pack/test/functional/apps/dataset_quality/degraded_field_flyout.ts\r\n```\r\n\r\nLet the test run and go green\r\n\r\n5. Navigate to `http://localhost:5620/app/management/data/data_quality/`\r\nusername - `test_user` and password - `changeme`\r\n\r\n6. Select the `degraded.dataset.rca` dataset\r\n\r\nYou will have an environment ready to test the flyout different\r\nscenarios\r\n\r\n## Demo\r\n\r\n## Field Limit and Ignore above isse\r\n\r\n![Field Limit\r\nIssue](https://github.com/user-attachments/assets/5908f1a8-ed85-455b-8f61-894b2fc6bb1c)\r\n\r\n## Warning about not current quality issue\r\n\r\n![Current Quality\r\nIssue](https://github.com/user-attachments/assets/1dd6278f-75f8-4715-bd83-8ac9784afbf7)\r\n\r\n## Blocker\r\n\r\nThere is an Elasticsearch issue on Serverless, which becomes a blocker\r\nfor merging this PR\r\n\r\nhttps://github.com/elastic/elasticsearch-serverless/issues/2815","sha":"0d19367fdfad5526b5220dfdf18b4991fe6b3abd","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["v9.0.0","release_note:feature","backport:prev-minor","ci:project-deploy-observability","Team:obs-ux-logs","Feature:Dataset Health"],"title":"[Dataset Quality] Implement _ignored root cause identification flow","number":192370,"url":"https://github.com/elastic/kibana/pull/192370","mergeCommit":{"message":"[Dataset Quality] Implement _ignored root cause identification flow (#192370)\n\n## Summary\r\n\r\nCloses - https://github.com/elastic/kibana/issues/192471\r\nCloses - https://github.com/elastic/kibana/issues/191055\r\n\r\nThe PR adds Flyout to the Degraded Fields inside the Dataset Quality\r\nDetails page where the Root Cause of the Degraded Field is diagnosed.\r\n\r\n## Pending Items\r\n\r\n- [x] API Tests for 1 new and 2 old API modifications\r\n- [x] E2E Tests for the Flyout\r\n\r\n## How to test this\r\n\r\nNOTE (Below guide is for Stateful, you can do the same for serverless)\r\n\r\n- Checkout the PR using - `gh pr checkout 192370`\r\n\r\n1. Start the FTR server using the command below\r\n\r\n```\r\n yarn test:ftr:server --config ./x-pack/test/functional/apps/dataset_quality/config.ts\r\n ```\r\n \r\n 2. Go to the following path - `x-pack/test/functional/apps/dataset_quality/degraded_field_flyout.ts`\r\n 3. Comment out the 2 `after` blocks present at Line - 54-56 and 414-416\r\n 4. Run the FTR runner using the command below\r\n \r\n ```\r\nyarn test:ftr:runner --config ./x-pack/test/functional/apps/dataset_quality/config.ts --include ./x-pack/test/functional/apps/dataset_quality/degraded_field_flyout.ts\r\n```\r\n\r\nLet the test run and go green\r\n\r\n5. Navigate to `http://localhost:5620/app/management/data/data_quality/`\r\nusername - `test_user` and password - `changeme`\r\n\r\n6. Select the `degraded.dataset.rca` dataset\r\n\r\nYou will have an environment ready to test the flyout different\r\nscenarios\r\n\r\n## Demo\r\n\r\n## Field Limit and Ignore above isse\r\n\r\n![Field Limit\r\nIssue](https://github.com/user-attachments/assets/5908f1a8-ed85-455b-8f61-894b2fc6bb1c)\r\n\r\n## Warning about not current quality issue\r\n\r\n![Current Quality\r\nIssue](https://github.com/user-attachments/assets/1dd6278f-75f8-4715-bd83-8ac9784afbf7)\r\n\r\n## Blocker\r\n\r\nThere is an Elasticsearch issue on Serverless, which becomes a blocker\r\nfor merging this PR\r\n\r\nhttps://github.com/elastic/elasticsearch-serverless/issues/2815","sha":"0d19367fdfad5526b5220dfdf18b4991fe6b3abd"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/192370","number":192370,"mergeCommit":{"message":"[Dataset Quality] Implement _ignored root cause identification flow (#192370)\n\n## Summary\r\n\r\nCloses - https://github.com/elastic/kibana/issues/192471\r\nCloses - https://github.com/elastic/kibana/issues/191055\r\n\r\nThe PR adds Flyout to the Degraded Fields inside the Dataset Quality\r\nDetails page where the Root Cause of the Degraded Field is diagnosed.\r\n\r\n## Pending Items\r\n\r\n- [x] API Tests for 1 new and 2 old API modifications\r\n- [x] E2E Tests for the Flyout\r\n\r\n## How to test this\r\n\r\nNOTE (Below guide is for Stateful, you can do the same for serverless)\r\n\r\n- Checkout the PR using - `gh pr checkout 192370`\r\n\r\n1. Start the FTR server using the command below\r\n\r\n```\r\n yarn test:ftr:server --config ./x-pack/test/functional/apps/dataset_quality/config.ts\r\n ```\r\n \r\n 2. Go to the following path - `x-pack/test/functional/apps/dataset_quality/degraded_field_flyout.ts`\r\n 3. Comment out the 2 `after` blocks present at Line - 54-56 and 414-416\r\n 4. Run the FTR runner using the command below\r\n \r\n ```\r\nyarn test:ftr:runner --config ./x-pack/test/functional/apps/dataset_quality/config.ts --include ./x-pack/test/functional/apps/dataset_quality/degraded_field_flyout.ts\r\n```\r\n\r\nLet the test run and go green\r\n\r\n5. Navigate to `http://localhost:5620/app/management/data/data_quality/`\r\nusername - `test_user` and password - `changeme`\r\n\r\n6. Select the `degraded.dataset.rca` dataset\r\n\r\nYou will have an environment ready to test the flyout different\r\nscenarios\r\n\r\n## Demo\r\n\r\n## Field Limit and Ignore above isse\r\n\r\n![Field Limit\r\nIssue](https://github.com/user-attachments/assets/5908f1a8-ed85-455b-8f61-894b2fc6bb1c)\r\n\r\n## Warning about not current quality issue\r\n\r\n![Current Quality\r\nIssue](https://github.com/user-attachments/assets/1dd6278f-75f8-4715-bd83-8ac9784afbf7)\r\n\r\n## Blocker\r\n\r\nThere is an Elasticsearch issue on Serverless, which becomes a blocker\r\nfor merging this PR\r\n\r\nhttps://github.com/elastic/elasticsearch-serverless/issues/2815","sha":"0d19367fdfad5526b5220dfdf18b4991fe6b3abd"}}]}] BACKPORT--> Co-authored-by: Achyut Jhunjhunwala <[email protected]>
- Loading branch information
1 parent
268e07f
commit 29be4a5
Showing
58 changed files
with
2,280 additions
and
445 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.