mirror of
https://github.com/monoscope-tech/monoscope.git
synced 2026-11-16 10:18:01 +00:00
feat(telemetry): write http.route to its promoted column on both legs
otel_metrics has carried `attributes___http___route` all along; the spans table was the outlier, so every query grouping endpoints by route paid a JSON extraction out of `attributes`. Order matters, and storage went first. TimeFusion's stored Delta schema was widened by `migrate-columns --add attributes___http___route:text` (92 -> 93 columns) before its YAML declared the column and before TF deployed — declaring it in YAML first is 7d68f01, `number of columns must match number of fields` on every INSERT. Migration 0141 is the Postgres half: `otelColumns` builds ONE insert statement for both dual-write legs, so a column one store has and the other does not fails every batch. Nullable everywhere, so no backfill: rows written before this read NULL, which is what "we did not capture the route" means.
This commit is contained in:
parent
e6a736438e
commit
4e9520ad83
3 changed files with 35 additions and 0 deletions
Loading…
Add table
Add a link
Reference in a new issue