[OneDiscover] Telemetry tasks

[kertal]

This is a placeholder issue to summarize the work that needs to be done to unify and extend Discover and Logs Explorer telemetry.

Tasks

Preview Give feedback

1. [OneDiscover] Add contextual awareness resolution results to EBT telemetry events #186109
   Project:OneDiscover Team:DataDiscovery impact:high telemetry +4
   
2. [OneDiscover] Add EBT event to track field usage #186156
   Project:OneDiscover Team:DataDiscovery +2
   
3. [Discover] Add EBT events to track contextual profile resolutions #200257
   Feature:Discover Project:OneDiscover Team:DataDiscovery impact:high telemetry +5
   
4. [discover] Add performance metrics #189457
   Feature:Discover Project:OneDiscover Team:DataDiscovery +3
5. [Discover] Report kibana:plugin_render_time metric event. #186129
   Feature:Discover Project:OneDiscover Team:DataDiscovery blocked impact:low impact:medium telemetry +7
   
6. [OneDiscover] Add EBT event to track field usage in KQL #194907
   Project:OneDiscover Team:DataDiscovery impact:low telemetry +4
7. [OneDiscover] Add EBT event to track field usage in ESQL #194909
   Project:OneDiscover Team:DataDiscovery impact:low +3

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[gbamparop]

@kertal do you think this should be part of the MVP? The initial telemetry scope was to adjust the dashboards we have for Logs Explorer to accommodate the URL change.

[ninoslavmiskovic]

@gbamparop @kertal The acceptance criteria for the MVP of telemetry is to cover everything we have aligned on in Phase 1 in telemetry (also new items) to have a full picture of "One Discover" when Phase 1 is launched. Additional is to unify the dashboards.

[gbamparop]

@ninoslavmiskovic let's keep working on the UI telemetry doc about what we'd like to track and then split it into two issues for MVP and for consolidating the dashboards as a follow-up.