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.

Sign up for GitHub

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

Jump to bottom

[Event-based Telemetry] Documentation & Dev Guides #121997

Closed
Tracked by #121992
afharo opened this issue Dec 24, 2021 · 3 comments
Closed
Tracked by #121992

[Event-based Telemetry] Documentation & Dev Guides #121997

afharo opened this issue Dec 24, 2021 · 3 comments
Assignees
@Bamieh
Labels
Feature:Telemetry impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@afharo
Copy link
Member

afharo commented Dec 24, 2021 •
edited
Loading

We should write clear documentation and Developer Guides to enable teams to instrument their own events.
@afharo afharo mentioned this issue Dec 24, 2021
Closed
30 tasks
@botelastic botelastic bot added the needs-team Issues missing a team label label Dec 24, 2021
@afharo afharo added Feature:Telemetry Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Dec 24, 2021
@elasticmachine
Copy link
Contributor

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

@botelastic botelastic bot removed the needs-team Issues missing a team label label Dec 24, 2021
@exalate-issue-sync exalate-issue-sync bot added impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort labels Dec 24, 2021
@afharo afharo changed the title [Event-based Telemetry] Dev Docs [Event-based Telemetry] Documentation & Dev Guides Feb 15, 2022
@exalate-issue-sync exalate-issue-sync bot added impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort and removed impact:needs-assessment Product and/or Engineering needs to evaluate the impact of the change. loe:small Small Level of Effort labels Mar 8, 2022
@afharo
Copy link
Member Author

afharo commented Mar 29, 2022

Important note: we should have a dedicated section to explain the key differences between EBT and Snapshot-based telemetry and more specifically UI/Usage counters to let devs decide which one fits their needs the better.

  1. EBT allows more granularity and more metadata to split and aggregate
  2. UI/Usage Counters can be sent even when the server is behind a firewall
  3. ...

@Bamieh
Copy link
Member

Bamieh commented Mar 31, 2022

@afharo good point i totally agree

@Bamieh Bamieh closed this as completed Jul 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Bamieh Bamieh

Labels
Feature:Telemetry impact:high Addressing this issue will have a high level of impact on the quality/strength of our product. loe:medium Medium Level of Effort Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@afharo @Bamieh @elasticmachine