App Health

Web analytics, product events, logs, and endpoint health in one workspace.

Maker note

Why I made this.

I built App Health because checking Sentry, PostHog, Slack, and cloud consoles separately made basic product health too fragmented.

Product contract

App Health helps product teams understand web traffic, intentional user actions, and application health across their projects.

For: Product managers, founders, and product teams; developers connect the instrumentation.
Outcome: See who is active as browser-session counts, which pages and named events are used, and whether backend failures explain product friction.
How: A small browser tracker and explicit named events feed workspace-scoped analytics; service SDKs and OTLP add aggregate endpoint health in the same dashboard.
Proof: Production Google signup, returning login, sign-out and project creation verified; own signup/project milestone logs remain exactly one each. Known analytics traffic returned 3 sessions, 4 page views and 2 named events without duplicate-batch inflation, with correct 1h/24h boundaries and referral sources. Public live page and revocation verified. JavaScript SDK 0.4.0 published and artifact integrity checked. See app-health/docs/release-2026-09-12.md; broader analytics parity and remotely published Swift package remain follow-up work.
Next action: Sign in with Google, add a project and environment, then install only the analytics, endpoint, or logging capability you need.

Public anatomy

Maintained evidence

Public destinations and repository evidence, when this project publishes them.

Repository publication

Public issues become a browsable, read-only record here. Open the source issue to comment, react, or follow the work.

The embedded reader is loading or unavailable. Read the issues in the source repository.

Every fact here comes from the project’s reviewed public record. Private work and operational controls stay private.