Add condaEnvCount and managerCount to pet.refresh telemetry#1626
Merged
eleanorjboyd merged 1 commit intoJul 6, 2026
Merged
Conversation
Adds environment-shape measures to the pet.refresh event so refresh duration can be sliced by total env count and conda footprint, to test whether the slow-refresh cohort is dominated by conda-heavy / many-env setups.
benvillalobos
approved these changes
Jul 6, 2026
Yoyokrazy
approved these changes
Jul 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two environment-shape measures to the
pet.refreshtelemetry event:condaEnvCount— number of discovered environments whose kind is CondamanagerCount— number of discovered environment managersThe event already carries
envCount(total discovered environments) andDuration. Together with the two new measures, we can slice refresh duration by total env count and conda footprint in telemetry, directly testing the open hypothesis that the slow-refresh cohort is dominated by conda-heavy / many-env setups.Motivation
We have an unexplained elevation in bad-experience rates that our simpler hypotheses (experiment ramp, first-run cost, PET code regression) did not account for. The remaining signal points at engaged users with complex setups, suspected conda-heavy — but we can't confirm this per-session without instrumenting the shape of what PET discovers. This is a minimal instrumentation change to unblock a confident decision (and to later verify whether lazy-Conda helps the right sub-cohort).
Notes