Unified Integrations View - Improve telemetry on integration funnel

[alexfrancoeur]

Opening this up placeholder as a nice to have for 7.16. We discussed capturing intent. ui_counters might be a good way to collect that information with an already existing collection mechanism.

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[joshdover]

A few suggestions:

• In order to support user funnels we should add a data-test-subj="integration-card-<id>" attribute to the integration card divs so can determine which integrations users are clicking on.
  • Goal of this is to allow us to segment our behavior analytics funnels that we track on Cloud by integration
  • Our analytics tool on Cloud supports CSS selectors so we can extract events based on [data-test-subj^=integration-card] for all clicks on these cards as well as segment based on specific cards we're interested in with [data-test-subj=integration-card-nginx]
• Using ui_counters will be a bit tricky, but I think with some intelligent naming scheme we'll be able to track what we want:
  • If we name the event something of the form integration:card:<id> we should be able to match and aggregate on integration:card:* for all clicks on these cards and integration:card:nginx for a specific integration we're interested in.
  • @afharo to check me on this, given the eventual indexing strategy to be completed in [I18n] Inject Intl Polyfill to PhantomJS #25465
  • These counts are aggregated on a daily basis, so we will not be able to do any finer-grained analysis.

[alexfrancoeur]

@joshdover both suggestions work for me. The benefit of having collection internal to Kibana is correlation with other Elasticsearch usage metrics. Did intent actually lead to ingestion. ui_counters felt like the easiest implementation, but definitely open to other suggestions. If it's too much work and out of scope for 7.16, I think data-test-subj will give us a lot and I like the segmentation strategy you suggested.