Telemetry for Dynamic Actions (Drilldowns)

[streamich]

Summary

Closes #78402

This PR integrate .telemetry() from PersistedState service to track the following metrics.

• 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 saved objects have.
  • Track what type of drilldown are used.

---

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

For maintainers

• This was checked for breaking API changes and was labeled appropriately

---

Release note

Adds telemetry tracking for dynamic UI Actions. Now number of drilldowns used on dashboard and type of the drilldowns is aggregated and reported using telemetry.

---

Documentation

Dynamic Actions Telemetry

Dynamic actions (drilldowns) report telemetry. Below is the summary of dynamic action metrics that are reported using telemetry.

Dynamic action count

Total count of dynamic actions (drilldowns) on a saved object.

dynamicActions.count

Count by factory ID

Count of active dynamic actions (drilldowns) on a saved object by factory ID (drilldown type).

dynamicActions.actions.<factory_id>.count

For example:

dynamicActions.actions.DASHBOARD_TO_DASHBOARD_DRILLDOWN.count
dynamicActions.actions.URL_DRILLDOWN.count

Count by trigger

Count of active dynamic actions (drilldowns) on a saved object by a trigger to which they are attached.

dynamicActions.triggers.<trigger>.count

For example:

dynamicActions.triggers.VALUE_CLICK_TRIGGER.count
dynamicActions.triggers.RANGE_SELECT_TRIGGER.count

Count by factory and trigger

Count of active dynamic actions (drilldowns) on a saved object by a factory ID and trigger ID.

dynamicActions.action_triggers.<factory_id>_<trigger>.count

For example:

dynamicActions.action_triggers.DASHBOARD_TO_DASHBOARD_DRILLDOWN_VALUE_CLICK_TRIGGER.count
dynamicActions.action_triggers.DASHBOARD_TO_DASHBOARD_DRILLDOWN_RANGE_SELECT_TRIGGER.count
dynamicActions.action_triggers.URL_DRILLDOWN_VALUE_CLICK_TRIGGER.count

Factory metrics

Each dynamic action factory (drilldown type) can report its own stats, which is
done using the .telemetry() method on dynamic action factories.

[elasticmachine]

Pinging @elastic/kibana-app-services (Team:AppServices)

[ppisljar]

the telemetry function should work like a reduce, where your stats argument is the accumulator, and i think we should do that on inner layers as well.

[ppisljar]

code LGTM

[kibanamachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: b640c3a
• Pipeline Steps (look for red circles / failed steps)
• Interpreting CI Failures

Failed CI Steps

• Setup Build Environment and Dependencies
• Setup Build Environment and Dependencies

Metrics [docs]

‼️ ERROR: no builds found for mergeBase sha [2ad3d2b]

History

• 💚 Build #91339 succeeded b640c3a
• 💚 Build #91034 succeeded ed23c11
• 💔 Build #91022 failed a186c7a
• 💚 Build #90996 succeeded 2af1bc4

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