Telemetry for Drilldowns

[Dosant]

• Use .telemetry() method of persistable state service which is wired into ui_actions_enhanced.
  • Track if saved object has a drilldown.
  • Track how many drilldowns a saved object have.
  • Track what type of drilldown are used.

---

Below is what we would like to track for drilldowns, but currently not possible because telemetry uiMetric is being rewritten now and is expected to be ready by 7.12.

• What % of customers are using drilldowns?
  • How many drilldowns are configured on a cluster, by type
• How many drills on average in a session? How many dashboards?
  • Every time a user executes a drilldown
  • Increase counter during session when action is executed
  • Can we have a flag for an action to opt into telemetry?
• How do we compare drill usage to filter usage? Time?
  • We need to brainstorm this one, it might not be possible.
• How long does it take a user to discover drilldowns are available?
  • Time from page load to drill action?
  • What other actions did they take?
• How often does the drill end in an error? 404?
  • Don’t think we can do this?
  • This will be important for API actions
• Is there any way we can store the number and type of parameters? Destination base url? Etc? (PII concern)
  • Does telemetry allow us to send extra metadata?
  • We don’t send the url, we send the list of fields used?
• How often do they search for help or ask for info in the configuration panel
• How often does someone start to configure and abandon without saving?

Further considerations:

• Do dashboards have drilldowns configured that are not used by other users?
• Is there a performance angle?
• How often is the user drilling and immediately going back to drill again to a different filter value on the same dashboard?

Related to: #50845

Part of: #42845

[elasticmachine]

Pinging @elastic/kibana-app-arch (Team:AppArch)