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/Monitoring] Monitoring should stop collecting Kibana Usage in the .monitoring indices #83521

Closed
3 tasks done
afharo opened this issue Nov 17, 2020 · 2 comments · Fixed by #84313
Closed
3 tasks done
Assignees
Labels
Feature:Stack Monitoring Feature:Telemetry Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@afharo
Copy link
Member

afharo commented Nov 17, 2020

Monitoring is collecting Kibana's Usage and storing them in the .monitoring indices:

  • bulk_uploader is using usageCollection's APIs to retrieve the usage data every 24h.
  • Metricbeat is calling /api/stats?extended&exclude_usage=false&legacy every 24h.

With the latest changes in #82638, it won't be needed anymore.

Planned action points (separate PRs):

@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-telemetry (Team:KibanaTelemetry)

@afharo afharo assigned Bamieh and afharo and unassigned Bamieh Nov 17, 2020
@afharo afharo changed the title [Telemetry/Monitoring] Change bulk_uploader's implementation to stop using usageCollection [Telemetry/Monitoring] Monitoring should stop collecting Kibana Usage in the .monitoring indices Nov 18, 2020
@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:Stack Monitoring 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