chore: remove usage for stats endpoint#151082
Conversation
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
|
buildkite test this |
|
@elasticmachine run elasticsearch-ci/docs |
@nnacin did you run |
|
@elasticmachine run elasticsearch-ci/docs |
|
buildkite test this |
|
@nnacin let me know if you can't see the CI errors. I can help you with highlighting what's failing. |
Thank you @afharo ! I can see the failures, I was working on fixing some. But I have a question, is my approach correct, should I remove completely the property |
TBH, I don't have a strong preference. However, looking at the current behavior, even when usage is not requested, this API returns an empty object. I wonder if returning it as empty is the least impactful change. What do you think? |
…-usage' into chore-150429/remove-usage
|
buildkite test this |
1 similar comment
|
buildkite test this |
| .then(({ body }) => { | ||
| expect(body.cluster_uuid).to.be.a('string'); | ||
| expect(body.usage).to.be.an('object'); // no usage collectors have been registered so usage is an empty object | ||
| expect(body.usage).to.eql({}); |
…-usage' into chore-150429/remove-usage
|
@elasticmachine merge upstream |
|
buildkite test this |
|
@elasticmachine run elasticsearch-ci/docs |
|
@nnacin, it looks like everything is ready to send this PR to review. Isn't it? |
|
@nnacin, great call! I commented on those 🙂 Feel free to mark it as ready to review whenever you are comfortable with it. |
Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
|
@elasticmachine run elasticsearch-ci/docs |
|
buildkite test this |
💚 Build Succeeded
Metrics [docs]Unknown metric groupsESLint disabled line counts
Total ESLint disabled count
History
To update your PR or re-run it, just comment with: |
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com> Co-authored-by: Alejandro Fernández Haro <afharo@gmail.com>
|
Pinging @elastic/kibana-core (Team:Core) |
Summary
Closes #150429
Do not extend the payload with telemetry usage.
Checklist
Delete any items that are not applicable to this PR.
Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.
When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:
For maintainers