-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
Usage-based telemetry #52515
Labels
discuss
enhancement
New value added to drive a business result
Feature:Telemetry
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Comments
epixa
added
enhancement
New value added to drive a business result
Feature:Telemetry
Team:Pulse
labels
Dec 9, 2019
Pinging @elastic/pulse (Team:Pulse) |
I think we can close this out in favor of #60984. This will be another endpoint in Kibana hit directly instead of leveraging Pulse (though we may want to consume in a Pulse channel as well). What do you think @TinaHeiligers ? |
@alexfrancoeur I agree. |
lukeelmers
added
the
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
label
Oct 1, 2021
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
discuss
enhancement
New value added to drive a business result
Feature:Telemetry
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Kibana should send usage flags for specific features in telemetry. This issue is just a stub for now as we work out the details.
The text was updated successfully, but these errors were encountered: