[TH-8479] OSS customer journey analytics MVP

Open
#3,406 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

The payload names no files, tests or entry points. Start by locating the existing six-hour aggregate heartbeat and the signup, login and API-key boundaries in the codebase, since the issue treats the heartbeat as reconciliation only. Done means the acceptance criteria hold: a signed, actor-aware event stream, opt-out that clears buffers, and coverage of the authenticated request boundary. The cloud receiver is a paired private change, so this cannot be finished from the public repository alone.

Written by the indexing model from the issue text.

Description

accepted

Context

OSS customer analytics currently has a six-hour aggregate heartbeat but no actor-aware journey stream. Sales and adoption analysis needs install, signup/login, API-key, agent/MCP, and authenticated request signals without collecting prompts, completions, traces, request bodies, or secrets.

MVP acceptance criteria

  • Self-hosted installs emit a durable, signed, actor-aware event stream.
  • Human users, API keys, agents, MCP clients, and system actors are representable without a human DB row.
  • Signup/login/account and authenticated request boundaries are covered; the existing six-hour heartbeat remains reconciliation only.
  • Opt-out clears event and heartbeat buffers and prevents journey events.
  • The cloud receiver/warehouse projection lands as the paired private EE change.
  • Deeper product-improvement telemetry is a follow-up phase with explicit disclosure.

Linear: TH-8479 — OSS customer analytics MVP: actor-aware journey events and durable delivery.

Dominant language
Python
Stars
2k
Forks
628
Avg merge
2d 2h
Merged PRs (30d)
259

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from future-agi/future-agi

All issues in future-agi/future-agi

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.