“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.
- His published feedback specifically mentions logs, tracked events, the SQL workbench, flexible schemas, the REST query API, and reports delivered to Slack.
- The statement describes workflow fit rather than a benchmark or guaranteed performance result.
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.
Let schemas evolve deliberately
Starting without a rigid up-front warehouse model does not mean ignoring types. Send test events, inspect the inferred schema, and keep existing field types stable as new context is added.
Automate the reviewed query
Once a query answers the right question, call it asynchronously or on a schedule and deliver the compact result where the team already works. Keep the saved SQL as the auditable source.
Evaluation blueprint
Turn the workflow into evidence you can verify
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 contract
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 contract
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 contract
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.
Related product capability
Continue this workflow in Alerts
Promote the reviewed reliability query into an owned threshold and response workflow.
Try the same event-to-answer workflow
Create an API key, instrument one meaningful workflow, and turn the first reviewed query into a chart or report.
More customer stories
Browserflow: From business events to answers that are easy to seeLogSnag: From raw event delivery to an answer the team can use