Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[EBT] Schema extraction tool #132249

Open
1 task
Tracked by #121992
afharo opened this issue May 16, 2022 · 2 comments
Open
1 task
Tracked by #121992

[EBT] Schema extraction tool #132249

afharo opened this issue May 16, 2022 · 2 comments
Labels
Feature:Telemetry Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@afharo
Copy link
Member

afharo commented May 16, 2022

Similar to @kbn/telemetry-tools, we should build an extraction tool that collects all the Event-type and Context Providers registrations and summarizes them in a JSON file that can be used by the Platform Analytics team to know the expected structure of the payloads to be sent. This will help them build better documentation and testing tools on their end (as they currently do with the Snapshot telemetry schemas).

Open Questions:

  • Should it be part of the existing @kbn/telemetry-tools? Or should it be part of the EBT package?
@afharo afharo changed the title Schema extraction tool: build a detailed list of <code class="notranslate">{ [event-type]: schema }` and another one from the context providers. [EBT] Schema extraction tool May 16, 2022
@botelastic botelastic bot added the needs-team Issues missing a team label label May 16, 2022
@afharo afharo added Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:Telemetry labels May 16, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-core (Team:Core)

@botelastic botelastic bot removed the needs-team Issues missing a team label label May 16, 2022
@pgayvallet
Copy link
Contributor

Should it be part of the existing @kbn/telemetry-tools? Or should it be part of the EBT package?

No strong opinion on this one, but given we have a dedicated 'package group' for EBT, I feel like it would make sense for the feature to have its own @kbn/analytics-tools package?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:Telemetry Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

No branches or pull requests

3 participants