Feat/backend telemetry v0#307
Open
laxmanclo wants to merge 8 commits into
Open
Conversation
Author
|
@AgentWrapper can you review this PR? |
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.
Implemented end-to-end telemetry for the rewrite on feat/backend-telemetry-v0.
This adds local SQLite telemetry plus optional PostHog export in the Go daemon, wires core backend events (daemon.started, cli.invoked, usage errors, spawn success/failure, 5xx, panic, project/onboarding, waiting-input dwell), and adds renderer-side PostHog analytics/error capture in Electron. The desktop app now ships with org-owned PostHog defaults, shares one stable install identity across backend + renderer, and emits a canonical ao.app.active event so DAU/WAU can be charted cleanly in PostHog.