From d749bf0b2738a1211410e3cd4f33e9479b835ee8 Mon Sep 17 00:00:00 2001 From: Zaeem Athar Date: Mon, 11 Mar 2024 09:58:28 +0100 Subject: [PATCH] Fixing note formatting. --- .../blog/2024-03-11-moving-away-from-segment.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/docs/website/blog/2024-03-11-moving-away-from-segment.md b/docs/website/blog/2024-03-11-moving-away-from-segment.md index d1eac7b7e0..7198af6d9a 100644 --- a/docs/website/blog/2024-03-11-moving-away-from-segment.md +++ b/docs/website/blog/2024-03-11-moving-away-from-segment.md @@ -16,7 +16,7 @@ TL;DR: This blog post introduces a cost-effective solution for event streaming t ## The Segment Problem Event tracking is a complicated problem for which there exist many solutions. One such solution is Segment, which offers ample startup credits to organizations looking to set up event ingestion pipelines. Segment is used for a variety of purposes, including web analytics. - +::: The price of **$1000/month** for 100k tracked users doesn’t seem excessive, given the complexity of the task at hand. @@ -203,7 +203,7 @@ Currently, our telemetry tracks 50,000 anonymized devices each month on a 1:60 d Cloud Functions is by far the most expensive service used by our pipeline. It is billed based on the vCPU / memory, compute time, and number of invocations. - +::: ## In Conclusion