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

[Backport 5.0] Simplify telemetry structure; eliminate difference between critical and non-critical telemetry #49610

Merged
merged 1 commit into from
Mar 17, 2023

Conversation

github-actions[bot]
Copy link
Contributor

Proof of concept PR here. I'm failing in Buildkite and am struggling resolving some of them (I can't even seem to get prettier to run anymore, it's been too long). I would love to work with @andersonlauren and @ryphil to (1) make specific reductions to our telemetry as part of this or soon after, and (2) get eng support to fully clean up and remove the old config option.

Test plan

  • Run a local instance, set disableNonCriticalTelemetry to true
  • See if any errors appear
  • Confirm telemetry sent is identical regardless of the value of the configuration option above

<!-- All pull requests REQUIRE a test plan: https://docs.sourcegraph.com/dev/background-information/testing_principles -->

Backport 0337361 from #48866

…nd non-critical telemetry (#48866)

Proof of concept PR here. I'm failing in Buildkite and am struggling
resolving some of them (I can't even seem to get prettier to run
anymore, it's been too long). I would love to work with @andersonlauren
and @ryphil to (1) make specific reductions to our telemetry as part of
this or soon after, and (2) get eng support to fully clean up and remove
the old config option.

## Test plan

* Run a local instance, set disableNonCriticalTelemetry to true
* See if any errors appear
* Confirm telemetry sent is identical regardless of the value of the
configuration option above

<!-- All pull requests REQUIRE a test plan:
https://docs.sourcegraph.com/dev/background-information/testing_principles
-->

---------

Co-authored-by: Aditya Kalia <32119652+akalia25@users.noreply.github.com>
Co-authored-by: Joe Chen <joe@sourcegraph.com>
(cherry picked from commit 0337361)
@github-advanced-security
Copy link

You have successfully added a new SonarCloud configuration ``. As part of the setup process, we have scanned this repository and found no existing alerts. In the future, you will see all code scanning alerts on the repository Security tab.

@sg-e2e-regression-test-bob

Bundle size report 📦

Initial size Total size Async size Modules
1.57% (+48.55 kb) 🔺 0.10% (+13.96 kb) 🔺 -0.30% (-34.59 kb) 🔽 -0.14% (-1) 🔽

Look at the Statoscope report for a full comparison between the commits 44f3406 and 530863b or learn more.

Open explanation
  • Initial size is the size of the initial bundle (the one that is loaded when you open the page)
  • Total size is the size of the initial bundle + all the async loaded chunks
  • Async size is the size of all the async loaded chunks
  • Modules is the number of modules in the initial bundle

@dadlerj dadlerj merged commit 1209ac1 into 5.0 Mar 17, 2023
@dadlerj dadlerj deleted the backport-48866-to-5.0 branch March 17, 2023 19:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants