[Meta] Telemetry & Usage Collection Tech-debt items #91611
Labels
Feature:Telemetry
Meta
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
technical debt
Improvement of the software architecture and operational architecture
@afharo Would it make sense to open a meta issue for general Telemetry-related cleanup tasks we feel are needed before 8.0? To me, it would be a nice way to track all the things that we should be doing before then.
Originally posted by @TinaHeiligers in #91464 (comment)
This issue is to track all the APIs and pieces of logic that are maintained in the Telemetry & Usage Collection plugins but we no longer use, or things we did one way because of some limitations back there, but we're OK to do it better now:
__LEGACY.appChanged
([Application Usage] Remove deprecated & unused legacy.appChanged API #91464)applicationUsageTracker
([Usage Collection] Remove unusedapplicationUsageTracker
from Public API #92670)any
([Telemetry] Remove uses ofany
in the Telemetry & Usage Collection plugins and libraries #93183)import type
andexport type
where possible ([Telemetry] Enforce use ofimport type
andexport type
#93184)telemetry_management_section
into thetelemetry
plugin (could be done as part of [Telemetry] Telemetry Advanced settings section should use the regular UI registration API #56498)telemetry_collection_manager
in favour of a better X-Pack extension API in thetelemetry
plugin (Removetelemetry_collection_manager
in favour of a better X-Pack extension API in thetelemetry
plugin #93185)kibana_system
([Telemetry] Test helpers forkibana_system
#92825)The text was updated successfully, but these errors were encountered: