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

[Telemetry] Add documentation about Application Usage #66783

Closed
afharo opened this issue May 15, 2020 · 3 comments · Fixed by #70624
Closed

[Telemetry] Add documentation about Application Usage #66783

afharo opened this issue May 15, 2020 · 3 comments · Fixed by #70624
Assignees
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 15, 2020

Some folks are asking to the telemetry team about how they can make use of or enable the Application Usage telemetry feature for their plugin.

Let's write some documentation to make it clear that it's automatic based on the KP routing and they don't need to set anything up on their end.

Additionally, let's use this issue to extend the docs of the plugin kibana_usage_collection. Maybe adding some links to other READMEs would be enough.

@elasticmachine
Copy link
Contributor

Pinging @elastic/pulse (Team:Pulse)

@afharo afharo self-assigned this Jul 2, 2020
@afharo
Copy link
Member Author

afharo commented Jul 2, 2020

Remember to add also documentation about the usage of the SavedObjects: #70475 (review)

@lukeelmers lukeelmers added the Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc label Oct 1, 2021
@elasticmachine
Copy link
Contributor

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

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

Successfully merging a pull request may close this issue.

4 participants