"Telemetry is my go-to for dumping logs and tracking events. It's straightforward, the SQL workbench is fast, and I don't have to worry about the schema upfront. Running SQL over a REST API lets me fetch data and dump reports straight to Slack. It's the essentials of what Sentry did for me."
Prem Viswanathan
Founder, SwiftCXConfirmed context
This page separates published feedback from the general pattern other teams can apply.
- Prem Viswanathan is the founder of SwiftCX.
- He uses the SQL workbench and REST API to query logs and events, then sends reports to Slack.
- He describes his workflow. The quote includes no benchmark timings or performance guarantees.
Repeatable pattern
How a team with the same need can start
Use one event path for investigation and reporting
A team with similar requirements can log operational events once, inspect them interactively, and reuse reviewed SQL through an API for scheduled reports.
Check field types as the schema changes
Send test events and inspect the schema Telemetry creates. Keep existing field types stable when you add fields so saved queries continue to work.
Schedule reports from the checked query
Once you have checked a query, run it asynchronously or on a schedule. Send the results to your team and keep the SQL so they can reproduce the report.
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
Can one event path support investigation and reporting?
operation_completed with operation, status, duration_ms, release, environment, and safe correlation fields
Validation check
Compare interactive SQL and Query API output for the same fixed time window and parameters.
Question and event fields
Can the event schema evolve without breaking saved reports?
Add optional typed context while keeping existing field names and types stable; record schema_version
Validation check
Replay old and new synthetic events, inspect null behavior, and run the existing report query over both versions.
Question and event fields
Is an automated report traceable?
Keep the saved query identifier, report window, generated_at time, row count, and delivery status
Validation check
Re-run the same query manually and compare the compact result before relying on scheduled delivery.
SQL recipes for this workflow
Measure background job retry and failure rate
Find unreliable jobs by comparing successful runs, retries, failures, and tail duration.
Measure webhook retry recovery
Separate permanent webhook failures from deliveries that recovered on a later attempt.
Calculate p50, p95, and p99 API latency
Compare median and tail latency by endpoint with DataFusion-compatible percentile SQL.
Use these queries in Telemetry
Learn about Alerts
Add a threshold and recipients to your reliability query to get alerts.
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
Browserflow: Track business activity and see what changedLogSnag: Send events, then query what happened