-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Do not return usage in GET /api/stats
#150429
Comments
Pinging @elastic/kibana-core (Team:Core) |
Is this issue available to be worked on? |
@nnacin, absolutely! Feel free to take it! PRs are always welcomed 🧡 |
maybe we need to change this default too |
Let me know we need to change false to true |
@MohitBansal321, it looks like @nnacin has a PR almost ready. Thank you both for contributing 🧡 |
It is okay if someone works on it that's good |
But don't do this assign someone other and again unassign |
Apologies! 🙏 |
It's okay @afharo let's connect on github |
TL;DR:
We should stop returning the usage data in the
GET /api/stats
: Dismiss the query parameterexclude_usage
, and always behave asexclude_usage=true
.Why?
In the past, we used the monitoring infrastructure to collect and send telemetry (Product Usage). This API helped with returning the Snapshot Telemetry information when requested with the query parameter
?exclude_usage=false
.However, as our product telemetry grew, the generation of the report took longer, creating issues in the frequency we poll info for monitoring (10s by default).
Metricbeat stopped polling for that info in 7.11 (it always sets
exclude_usage=true
), but we never removed the capability in Kibana for backwards compatibility. When analyzing support requests, we've realized there are some external services that abuse this API by callingexclude_usage=false
. I think it's time we completely decouple this API (intended for monitoring) and the usage data.Implementation details:
For the purpose of backwards compatibility, we should support the query parameter (allow it to be
true
/false
), but Kibana would dismiss the parameter and act as if it's alwaystrue
(do not extend the payload with telemetry usage):https://github.com/elastic/kibana/blob/main/src/plugins/usage_collection/server/routes/stats/stats.ts#L88
Follow ups:
Potentially, we could also apply the changes below, but I'd rather create follow-up issues to keep the scope of this task controlled.
The text was updated successfully, but these errors were encountered: