Skip to content

Use InfluxDB v3 API for analytics reporting - #23620

Draft
SMillerDev wants to merge 3 commits into
mainfrom
SMillerDev-patch-1
Draft

Use InfluxDB v3 API for analytics reporting#23620
SMillerDev wants to merge 3 commits into
mainfrom
SMillerDev-patch-1

Conversation

@SMillerDev

@SMillerDev SMillerDev commented Aug 22, 2026

Copy link
Copy Markdown
Member

  • Have you followed our Contributing guidelines?
  • Have you checked for other open Pull Requests for the same change?
  • Have you explained what your changes do? Performance claims (e.g. "this is faster") must include brew benchmark results.
  • Have you explained why you'd like these changes included, not just what they do?
  • For bug fixes, have you given step-by-step brew commands to reproduce the bug?
  • Have you written new tests (excluding integration tests)? Here's an example.
  • Have you successfully run brew lgtm (style, typechecking and tests) locally?

  • I did not use AI/LLM to create this PR, or I disclosed the tool/model below and reviewed its output; I did not attribute commits to AI and will answer maintainer questions and review comments myself without AI/LLM.

This makes sure we're using the most modern API to write analytics data. Just to keep up to date.

TODO:

  • Change URL to the new brew.sh endpoint
  • Remove authorization header because it has a fallback with the new endpoint, can also be a followup

…sertion

Co-authored-by: SMillerDev <1484494+SMillerDev@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants