Skip to content

Feature/extended telemetry - #129

Closed
marisbv wants to merge 4 commits into
mainfrom
feature/extended-telemetry
Closed

marisbv wants to merge 4 commits into
mainfrom
feature/extended-telemetry

Conversation

@marisbv

@marisbv marisbv commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

d2a2c70 Document the telemetry rules in AGENTS.md
cc10011 Report query shape and feature use at call sites
4f47c63 Carry query shape and client context in events
0b4c454 Add Telemetry settings group and query opt-out

"Send query telemetry" governs the table, column and filter values
that a query event carries. The main switch keeps working on its own,
so a user can report usage without reporting content.
The studio_telemetry table takes no new columns, so every new field
goes in props. The server drops a props object above its cap instead
of cutting it, so fitProps degrades the object in steps first.
Eleven of eighteen routes sent only a page view. The node, browser,
builder and workbench events fill that gap, and every query event now
carries the table, the columns and the filters that ran.
The event name list is closed on both sides, and the table takes no
new columns. Both facts cost a silent data loss when missed.
@marisbv marisbv closed this Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants