Configure hosted-dev Exie telemetry - #2639
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
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
1 participant
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.
Hosted dev served an empty browser telemetry API key, so Exie conversation sharing produced no events or sessions. Configure the existing public, client-scoped ingestion key for the dev Exceptionless project in
k8s/ex-dev-values.yaml, and set its internal project ID so jobs suppress self-telemetry processing logs. The existing ConfigMap checksum triggers the deployment rollout.Also wait for the separate OAuth test host to become ready before sending discovery requests, fixing the startup race exposed by CI. Production configuration and API contracts are unchanged.
Validation: the enabled client-only key belongs to project
6ac286ada7bf6e0001a886cfand returned HTTP 200 for project configuration. Helm lint and render/startup checks passed. All 76 OAuth endpoint tests passed locally in 35.7 seconds. Full CI passed at760d415e8in 8m18s (run). End-to-end event delivery remains to be verified after merge and deployment.