"Telemetry makes it super easy to track, analyze, and visualize what's going on in my business. It's the perfect mix of simple and powerful."
Namu Kang
Founder, BrowserflowConfirmed context
This page separates published feedback from the general pattern other teams can apply.
- Namu Kang is the founder of Browserflow.
- He describes tracking events, analyzing them, and charting the results.
- His feedback covers ease of use. It includes no deployment size or measured results.
Repeatable pattern
How a team with the same need can start
Log completed work
Start with events for completed work, failures, revenue, and customer milestones. Choose the events that answer your first business question.
Save the result as a chart
Save the query result as a chart or table. Add breakdowns that help explain changes in the main metric.
Keep raw events available
Keep the SQL and event rows behind each chart available. When a number changes, you can check what happened.
Try a similar workflow
Test the workflow with your own events
The examples below are a practical evaluation plan derived from the published workflow. They are not claims about the customer's implementation, event schema, or results.
Question and event fields
Which completed business workflows changed this week?
workflow_completed with workflow, status, duration_ms, account_id, source, and timestamp_utc
Validation check
Reconcile a small fixture with known completed and failed outcomes before charting the weekly trend.
Question and event fields
Where does activation lose qualified accounts?
signup_completed, integration_connected, and activation_completed with account_id, source, plan, and milestone_version
Validation check
Confirm that every account is counted once per milestone and that each cohort has a complete observation window.
Question and event fields
Which visible change deserves investigation?
Keep release, environment, workflow, status, and a safe correlation identifier on the outcome event
Validation check
Open the exact rows behind an unusual chart bucket and verify the breakdown before acting.
SQL recipes for this workflow
Build a signup-to-activation funnel in SQL
Calculate unique-user conversion through signup, onboarding, integration, and first-value milestones.
Find features used before upgrade
Join feature events to upgrade events and rank behaviors that occur before paid conversion.
Calculate API error rate by route
Rank API routes by 5xx error rate. Exclude routes with fewer than 20 requests so one failure does not dominate the results.
Use these queries in Telemetry
Learn about Dashboards
Save a product or revenue query to a dashboard your team can check.
Send events and query the results
Create an API key, instrument one meaningful workflow, and turn the first reviewed query into a chart or report.
More customer stories
LogSnag: Send events, then query what happenedSwiftCX: A fast SQL workbench for logs, events, and automated reports