[CLN] Make telemetry a no-op

[kylediaz]

#6469

We do not collect telemetry anymore. This removes posthog as a dependency and makes the product telemetry impl a no-op.

I want to say on our docs that we do not collect telemetry, and I feel removing this instrumentation is a prerequisite.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[kylediaz]

• [CLN] Make telemetry a no-op #6362 👈 (View in Graphite)
• [TST] Make pytest use importlib #6483 : 3 other dependent PRs (#6489 , #6491 , #6497 )
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[blacksmith-sh]

Found 5 test failures on Blacksmith runners:

Failures

Test	View Logs
test_cycle_versions[version_settings1]	View Logs
test_cycle_versions[version_settings1]	View Logs
test_cycle_versions[version_settings2]	View Logs
test_cross_version_persist/test_cycle_versions[version_settings1][single-region]	View Logs
test_cross_version_persist/test_cycle_versions[version_settings2][single-region]	View Logs

[propel-code-bot]

Telemetry cleanup is nearly complete; remove redundant class and empty module for clarity.

Status: Minor Suggestions | Risk: Low

Issues Identified & Suggestions

• Remove redundant NoOp class, use base directly: chromadb/telemetry/product/__init__.py
• Delete emptied telemetry module to avoid dead stub: chromadb/telemetry/product/posthog.py

Review Details

📁 10 files reviewed | 💬 2 comments

👍 / 👎 individual comments to help improve reviews for you

[propel-code-bot]

[Maintainability] The ProductTelemetryClient class is now a concrete implementation that performs no operations (since the abstract method decorator was removed). This makes NoOpProductTelemetryClient redundant as it simply overrides the method with the same no-op behavior.

Since you are updating the configuration to point to a NoOp implementation anyway, you can simplify the architecture by:

1. Removing NoOpProductTelemetryClient entirely.
2. Using ProductTelemetryClient directly in the configuration default.

This reduces boilerplate and keeps the class hierarchy cleaner.

Context for Agents

The `ProductTelemetryClient` class is now a concrete implementation that performs no operations (since the abstract method decorator was removed). This makes `NoOpProductTelemetryClient` redundant as it simply overrides the method with the same no-op behavior.

Since you are updating the configuration to point to a NoOp implementation anyway, you can simplify the architecture by:
1. Removing `NoOpProductTelemetryClient` entirely.
2. Using `ProductTelemetryClient` directly in the configuration default.

This reduces boilerplate and keeps the class hierarchy cleaner.

File: chromadb/telemetry/product/__init__.py
Line: 42