Create Feature Adoption Dashboard on Looker

[Omolola-Akinleye]

Create a Feature Adoption Dashboard using the gold_cloud_security_feature_adoption and Wireframe

Definition of Done:

• Build Feature Adoption based on Wireframe
• Verify metrics are being tracked from Product's Cloud Native Capabilities Epic and below

Metric Requirements Feature Adoption:

• How many customers have installed the CSPM/KSPM integration?
• How many customers have installed the CSPM/KSPM integration with AWS, GCP, and or Azure selected as the cloud provider?
• How many of these customers selected the single account (AWS), project (GCP), or subscription (Azure) deployment option?
• How many of these customers selected the AWS organization, GCP organization, or Azure organization deployment option?
• How many customers have installed the CSPM integration for AWS, GCP, and or Azure with the cloud-native way of deploying (AWS CloudFormation, Google Cloud Shell script, Azure Cloud Shell script) as the selected setup option?
• How many customers have installed the CSPM integration for AWS, GCP, and or Azure with the manual way of deploying as the selected setup option?
• For customers who installed the CSPM/KSPM integration, how many were able to successfully deploy the elastic agent without generating findings?
• For customers who installed the CSPM/KSPM integration, how many were able to successfully deploy the elastic agent and generate findings?

Note: Feature Adoption doesn't include Vuln Mgmt or CWP.

Related Tickets:

• [Cloud Security][Telemetry] Create Gold Feature Adoption Table #167051 (comment)
• [Cloud Security][telemetry] cspm feature adoption planning #163758

Blocked Tickets:

• Fix Installation Stats Null values in Gold Feature Adoption Table #171404 blocks this feature because we are missing installation stats which help create charts so Credentials, Single vs Multi account, automatic vs manual setup.

[Omolola-Akinleye]

@kfirpeled @CohenIdo Just f.y.i we don't have customer data just yet until after 8.11.0. is released since we created a new telemetry collector. I can create the dashboard but it won't show any customer data thus charts will be broken.

[kfirpeled]

Hi @Omolola-Akinleye , in that case I'll postpone this task in a sprint (32)

[maxcold]

Low in prio while waiting for the new OKR - 3rd party adoption

[CohenIdo]

Telemetry sync: we agreed to take one day to build the dashboard and verify that data is collected as expected. In case of issues, document them and open a task if necessary.

@tehilashn @Omolola-Akinleye

[kfirpeled]

@Omolola-Akinleye , @CohenIdo I'm sorry but this task is missing DOD.
Can you please define what is are the dashboard requirements? what is the proposed design? what features are we going to track as a first step?
so we can assess properly this task estimation

[Omolola-Akinleye]

@kfirpeled DOD is updated to include KSPM and CSPM metric requirements, a proposed design, related ticket, and epics for context and timeline of decisions tracked. @kfirpeled @CohenIdo Requirements were done months ago keep in mind.

[kfirpeled]

Thanks @Omolola-Akinleye ,

number of questions:

1. Now that we have it written down can you confirm the estimation for the given wireframe and the proposed dashboard?
2. I suggest adding a checkpoint for this task, to provide a query to present the data in a tabular fashion. The rationale here is that we need to do it anyway and in case building the UI would take more time than we think. We could still enjoy the digested data results. wdyt? @CohenIdo , @tehilashn , @smriti0321

[Omolola-Akinleye]

@kfirpeled Hi Kfir, The ticket estimation is 3. I don't estimate more than 1-2 days.

[Omolola-Akinleye]

Known issues

• There are cases where Cloud account stats and installation stats will not share the same package_policy_id because package_policy_id was indexed in findings in 8.11.0 and Installation stats telemetry was release in 8.10.0. More details see comment here.
• There are still 4,000 records with null installation stats that will need further investigation and make take more analysis.

[kfirpeled]

As mentioned by @Omolola-Akinleye here
We Invested a couple of days to create the dashboard but it seems the complexity is bigger than we estimated.
As we agreed, I'm deprioritizing this issue for now