Repository navigation
Release 1.7.2: usage telemetry reports how projects build their physical tables - #210
Merged
Merged
Conversation
chore: sync main (v1.7.1) into develop
Adds two optional heartbeat fields so we can see which non-dbt sources the Physical stage should learn to read first: - physicalTools: dbt, sqlmesh, dataform, databricksBundle, fabric, powerBi, sqlProject, flyway, liquibase, alembic, prisma, django, rails, notebooks, ddlScripts, dbml - platforms: databricks, snowflake, bigquery, postgres, redshift, fabric, synapse, sqlserver, duckdb, spark, trino, athena, mysql, oracle, clickhouse, other Detection (src/services/physicalTooling.ts) is pure and returns only allowlisted values: marker file names plus a fixed pattern in the head of a few small files. The dbt warehouse comes from manifest.json's adapter_type; profiles.yml is never read. It runs 15 s after activation, once per workspace per UTC day, and not at all while telemetry is off. Absent means not looked; [] means looked and found nothing. Worker: allowlists, validation, D1 migration 0003 (physical_tools, platforms), tests. telemetry.json, telemetry/README.md and CHANGELOG updated. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…ling Telemetry: report how workspaces build their physical tables
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a patch release. The
## Unreleasedheading is left bare, sodeploy.ymlbumps it to 1.7.2.What ships
Physical tooling telemetry (PR Telemetry: report how workspaces build their physical tables #209): the daily heartbeat gains two optional fields:
physicalTools: dbt, SQLMesh, Dataform, Databricks bundle, Fabric, Power BI project, SQL project, Flyway, Liquibase, Alembic, Prisma, Django, Rails, notebooks,CREATE TABLEscripts, DBMLplatforms: Databricks, Snowflake, BigQuery, Postgres, Fabric, SQL Server, …Each is a fixed list, so we can choose which non-dbt sources the Physical stage should read next. Detection looks at file names and a fixed pattern in the head of a few small files, and never reads
profiles.yml. Nothing leaves the machine but allowlisted values.Deploy order
This change touches
telemetry/, sodeploy.ymlruns thetelemetry-workerjob first:0003_physical_tooling.sql(addsphysical_tools,platforms)The extension release waits on that job. An older Worker would only drop the new keys, never reject the heartbeat, so the order is a safety margin, not a hard requirement.
Compatibility
Nothing changes on disk. There are no
packages/changes, so nothing is published to npm and no Confluence follow-up is needed. The telemetry contract change is additive (HEARTBEAT_VERSIONstays 1; old clients store NULL).CI is green on #209.
🤖 Generated with Claude Code