Re:Show HN: Telemetry.sh – Simplifying Telemetry Measurement
by thebuilderjr on Monday August 05, 2024 @05:26PM
(#41165774)
The biggest advantage is simplicity. To log an object in your application with OpenTelemetry, you either need munge your data to adapt it to their spec or rewrite a lot of your application code using their span abstraction. In contrast, with Telemetry, you can ingest any object you already have in your code as JSON with a single line of code and start analyzing the data immediately. Moreover, our SQL API makes it easy to integrate this data into your product or internal dashboards, unlike tools like Mixpanel or Amplitude that offer similar ingest APIs but lack APIs for SQL querying.
[ Parent
| on HN ]
Re:Show HN: Telemetry.sh – Simplifying Telemetry Measurement
by irisguy on Tuesday August 06, 2024 @05:12AM
(#41169054)
How's it compare to Vercel's solution?: https://vercel.com/docs/analytics/custom-events
Re:Show HN: Telemetry.sh – Simplifying Telemetry Measurement
by thebuilderjr on Tuesday August 06, 2024 @08:27AM
(#41170203)
Vercel's custom events offer similar ingestion APIs, but their analysis capabilities are limited compared to Telemetry. With Vercel, you are confined to the predefined reports and graphs they provide. I firmly believe in the flexibility and extensibility of data, and there's no better way to achieve this than with a comprehensive SQL API, which Telemetry offers.