Skip to content
This repository was archived by the owner on Mar 31, 2026. It is now read-only.
This repository was archived by the owner on Mar 31, 2026. It is now read-only.

Discoverability and product telemetry #202

Closed as not planned
Closed as not planned

Description

@codeacula

We need better observability into Apollo's behavior so we can evaluate product viability with a small test group.\n\n## Goals\n\n- track operational behavior and failures across reminder, conversation, and AI flows\n- capture usage/engagement signals that help us understand whether features are working\n- avoid overbuilding a custom analytics system when an existing platform (such as PostHog) can cover the basics\n\n## Scope\n\n- structured logs around important workflow boundaries\n- token/cost usage where available from AI calls\n- reminder send / follow-up / acknowledgment / completion metrics\n- feature usage signals for setup, to-dos, reminders, and feedback loops\n- basic product analytics integration (PostHog or equivalent)\n\n## Notes\n\n- This supersedes the narrower PostHog-only issue #116.\n- Keep privacy and small-group testing needs in mind; start simple and useful.\n

Activity

  1. changed the title [-]Discoverability[/-] [+]Discoverability and product telemetry[/+] on Mar 22, 2026
  2. added this to the Viability milestone on Mar 22, 2026
  3. codeacula commented on Mar 22, 2026

    @codeacula
    OwnerAuthor

    Triage note: dashboard visibility has become a higher product priority. #95 is now the primary dashboard/UI issue for surfacing live system state and management, while this issue remains focused on the telemetry/observability data that should feed that dashboard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions