Skip to content

The only tool you need to know what is happening and how to fix it.

fix: for the root overload with native golang sdk + blog update

ddux81f3c0896442
diff --git a/backend/app/models/clientmodels/clientmodels.model.go b/backend/app/models/clientmodels/clientmodels.model.go
index 9d2ad617..683527ae 100644
--- a/backend/app/models/clientmodels/clientmodels.model.go
+++ b/backend/app/models/clientmodels/clientmodels.model.go
@@ -133,6 +133,7 @@ func (c *ClientTrace) ToEndpoint(appVersion, serverName string) models.Endpoint
ServerName: serverName,
DistributedTraceId: c.parsedDistributedTraceId(),
IsStream: c.Attributes[streamAttributeKey] == "true",
+ IsRoot: true,
}
}
@@ -147,6 +148,7 @@ func (c *ClientTrace) ToTask(appVersion, serverName string) models.Task {
AppVersion: appVersion,
ServerName: serverName,
DistributedTraceId: c.parsedDistributedTraceId(),
+ IsRoot: true,
}
}
diff --git a/website/content/blog/flutter-session-replay.mdx b/website/content/blog/flutter-session-replay.mdx
index 26d0162d..902b6417 100644
--- a/website/content/blog/flutter-session-replay.mdx
+++ b/website/content/blog/flutter-session-replay.mdx
@@ -155,6 +155,6 @@ If you see something that can be done better, open a PR. Every change gets measu
The next goal is equivalent implementations for iOS, Android, and React Native. If you work in any of those ecosystems and want to take a swing at it, reach out or open an issue. I’d rather build this together than alone.
-Special thanks to: u/chimbori, u/__o_ — _o__, u/Deep_Ad1959, u/g0rdan and everyone else from the FlutterDev community on Reddit, whose feedback directly shaped several of the optimizations described here.
+Special thanks to: u/chimbori, u/\_\_o\_ — \_o\_\_, u/Deep_Ad1959, u/g0rdan and everyone else from the FlutterDev community on Reddit, whose feedback directly shaped several of the optimizations described here.
The code is available in the [Traceway](https://github.com/tracewayapp/traceway) and [Traceway Flutter](https://github.com/tracewayapp/traceway-flutter) repositories. You can also reach out directly by sending me an email at [email protected] or adding me on [LinkedIn](https://www.linkedin.com/in/dusanstanojeviccs).
diff --git a/website/content/blog/sqlite-observability-stack.mdx b/website/content/blog/sqlite-observability-stack.mdx
index 6937695e..ad5eac96 100644
--- a/website/content/blog/sqlite-observability-stack.mdx
+++ b/website/content/blog/sqlite-observability-stack.mdx
@@ -2,7 +2,7 @@
title: "I Ran My Entire Observability Stack on SQLite. You Probably Could Too."
date: "2026-05-29"
category: "engineering"
-description: "Most observability stacks optimize for throughput your startup will never use. We optimized for accessibility instead — easy and cheap to run — and hit 58K metric points/sec anyway. Here is the full benchmark."
+description: "Most observability stacks optimize for throughput your startup will never use. We optimized for accessibility instead, easy and cheap to run, and hit 58K metric points/sec anyway. Here is the full benchmark."
---
## TL;DR
@@ -40,9 +40,9 @@ All of the tests have been performed on a dedicated-vCPU instance, specifically
We will be measuring throughput of metrics in three phases:
-1. **Large payload** — 16k max metric points per payload, 5 req/sec max
-2. **Largest sustainable payload, max request rate** — taking the largest sustainable payload we max out req/sec to find the breaking point
-3. **100 metric points per req** — how many requests per second can we ingest
+1. **Large payload** - 16k max metric points per payload, 5 req/sec max
+2. **Largest sustainable payload, max request rate** - taking the largest sustainable payload we max out req/sec to find the breaking point
+3. **100 metric points per req** - how many requests per second can we ingest
### What "accepted" means here