Telemetry

SwiftCX customer story

A fast SQL workbench for logs, events, and automated reports

SwiftCX founder Prem Viswanathan explains why straightforward ingestion, flexible schemas, fast SQL, and a query API make Telemetry useful in day-to-day operations.

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 of SwiftCX

Prem Viswanathan

Founder, SwiftCX

Confirmed 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

1

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.

2

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.

3

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.

SQL recipes for this 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.

Start free

More customer stories

Browserflow: From business events to answers that are easy to see