-
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
[Cloud Security] 3P Misconfiguration and vulnerabilities page empty state #193051
Conversation
Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security) |
@JordanSh If we are not releasing 3rd party features in the dashboard and benchmarks, are we ok with promoting 3rd party integrations on these pages empty states? might be confusing for users - you go and install wiz from the dashboard page but you don't see any wiz data there after |
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.
Product question, do we plan Learn more
link there to point to the docs? I think it's needed in the empty state to explain users that for Misconfigurations to show up they need specific version of the integration with cloud_configuration_finding
data stream enabled. It is possible that they already have this integration but of the older version or with only a specific data stream enabled say audit
which has nothing to do with our Findings. So seeing this empty state might be confusing for them if we only have link to "add integration"
<EuiFlexGroup> | ||
<EuiFlexItem> | ||
<EuiEmptyPrompt | ||
style={{ padding: 24 }} |
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.
any eui const to use here instead of hardcoding number?
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Module Count
Async chunks
Page load bundle
Unknown metric groupsmiscellaneous assets size
History
To update your PR or re-run it, just comment with: cc @JordanSh |
Dashboard has different mechanism since each integration has its own page. But i did remove this part from the rules page |
(cherry picked from commit 0212c69)
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…#194034) # Backport This will backport the following commits from `main` to `8.x`: - [[Cloud Security] 3P Misconfiguration page empty state (#193051)](#193051) <!--- Backport version: 9.4.3 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sqren/backport) <!--BACKPORT [{"author":{"name":"Jordan","email":"[email protected]"},"sourceCommit":{"committedDate":"2024-09-25T15:35:24Z","message":"[Cloud Security] 3P Misconfiguration page empty state (#193051)","sha":"0212c69e0ef5272bd93aa83e667dd57fadac1764","branchLabelMapping":{"^v9.0.0$":"main","^v8.16.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","Team:Cloud Security","backport:prev-minor"],"title":"[Cloud Security] 3P Misconfiguration page empty state","number":193051,"url":"https://github.com/elastic/kibana/pull/193051","mergeCommit":{"message":"[Cloud Security] 3P Misconfiguration page empty state (#193051)","sha":"0212c69e0ef5272bd93aa83e667dd57fadac1764"}},"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/193051","number":193051,"mergeCommit":{"message":"[Cloud Security] 3P Misconfiguration page empty state (#193051)","sha":"0212c69e0ef5272bd93aa83e667dd57fadac1764"}}]}] BACKPORT--> Co-authored-by: Jordan <[email protected]>
Summary
Resolves #187229
Resolves #190505
Screen.Recording.2024-09-16.at.19.12.15.mov