fix(telemetry): report every region to the one telemetry host - #224
Conversation
The global region profile pointed at telemetry-logs.pythinker.ai, a host that does not exist, so anyone whose install marker said 'global' sent telemetry into a dead name. There is one Pythinker telemetry host; drop the second endpoint and the install-marker selection that chose it.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
💤 Files with no reviewable changes (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughTelemetry now uses one shared ChangesTelemetry endpoint routing
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: 🔵 Low · up to Global telemetry will be sent to the shared .com endpoint instead of the previous .ai endpoint. The change is mergeable with explicit owner awareness that the destination has equivalent security, data-handling, and regional controls, including for queued telemetry during upgrades or rollback. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 4 files.
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
commit: |
[skip changeset] — no user-perceivable change: telemetry is invisible to users, and the affected path was already failing silently.
Summary by CodeRabbit
.comhost.