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

[Cloud Security] [Posture Dashboard] Update links to the findings page with groupBy option #176463

Merged

Conversation

opauloh
Copy link
Contributor

@opauloh opauloh commented Feb 8, 2024

Summary

It closes #173496

This PR updates the Cloud Posture Dashboard links to the findings page to leverage the new Grouping visualization.

Account Evaluated section links and Benchmarks on the Cloud Tab redirect to the Findings page Grouped by Cloud Account.

Account Evaluated section links and Benchmarks on the Kubernetes Tab redirect to the Findings page Grouped by Kubernetes Cluster.

Recording

Cloud Tab

Screen.Recording.2024-02-07.at.5.43.00.PM.mov

Kubernetes Tab

Screen.Recording.2024-02-07.at.5.43.27.PM.mov

@opauloh opauloh added release_note:skip Skip the PR/issue when compiling release notes Team:Cloud Security Cloud Security team related v8.13.0 labels Feb 8, 2024
@opauloh opauloh requested a review from JordanSh February 8, 2024 01:46
@opauloh opauloh requested a review from a team as a code owner February 8, 2024 01:46
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-cloud-security-posture (Team:Cloud Security)

@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #58 / aiops log rate analysis with 'kibana_sample_data_logstsdb' kibana sample data logs displays index details

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
cloudSecurityPosture 403.1KB 404.0KB +901.0B

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

Comment on lines 21 to +43
type: CIS_AWS,
name: 'Amazon Web Services (AWS)',
provider: 'aws',
name: getBenchmarkApplicableTo(CIS_AWS),
provider: CLOUD_PROVIDERS.AWS,
},
{
type: CIS_GCP,
name: 'Google Cloud Platform (GCP)',
provider: 'gcp',
name: getBenchmarkApplicableTo(CIS_GCP),
provider: CLOUD_PROVIDERS.GCP,
},
{
type: CIS_AZURE,
name: 'Azure',
provider: 'azure',
name: getBenchmarkApplicableTo(CIS_AZURE),
provider: CLOUD_PROVIDERS.AZURE,
},
{
type: CIS_K8S,
name: 'Kubernetes',
benchmarkId: 'cis_k8s',
name: getBenchmarkApplicableTo(CIS_K8S),
benchmarkId: CIS_K8S,
},
{
type: CIS_EKS,
name: 'Amazon Elastic Kubernetes Service (EKS)',
benchmarkId: 'cis_eks',
name: getBenchmarkApplicableTo(CIS_EKS),
benchmarkId: CIS_EKS,
Copy link
Contributor

Choose a reason for hiding this comment

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

i see that its not new, but can we change it so all of those uses benchmarkId to keep it consistent? not urgent

Comment on lines +82 to +85
return navToFindingsByCloudProvider(benchmark.provider);
}
if (benchmark.benchmarkId) {
navToFindingsByCisBenchmark(benchmark.benchmarkId);
return navToFindingsByCisBenchmark(benchmark.benchmarkId);
Copy link
Contributor

Choose a reason for hiding this comment

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

why do we need to return here? no one takes in the value and the functions themselves do not return anything. i think this is redundant.

@@ -57,7 +57,7 @@ const useNavigate = (pathname: string, dataViewId = SECURITY_DEFAULT_DATA_VIEW_I
const { services } = useKibana();

return useCallback(
(filterParams: NavFilter = {}) => {
(filterParams: NavFilter = {}, groupBy?: string[]) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

might be to read and use if this function will receive an object, not urgent since it will require some refactoring

@JordanSh JordanSh merged commit 3d431f3 into elastic:main Feb 8, 2024
24 checks passed
@kibanamachine kibanamachine added the backport:skip This commit does not require backporting label Feb 8, 2024
CoenWarmer pushed a commit to CoenWarmer/kibana that referenced this pull request Feb 15, 2024
fkanout pushed a commit to fkanout/kibana that referenced this pull request Mar 4, 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 release_note:skip Skip the PR/issue when compiling release notes Team:Cloud Security Cloud Security team related v8.13.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Cloud Posture] Dashboard Improvements - linking to findings page
5 participants