Skip to content

Instantly share code, notes, and snippets.

@aaronschachter
Created June 9, 2026 21:16
Show Gist options
  • Select an option

  • Save aaronschachter/ce13de0c49617d69415ce2fe0c0c0b6b to your computer and use it in GitHub Desktop.

Select an option

Save aaronschachter/ce13de0c49617d69415ce2fe0c0c0b6b to your computer and use it in GitHub Desktop.
DDA Query Builder Rollout Monitoring - CMSEXT-2041

DDA Query Builder Rollout Monitoring

Merged PRs (2026-06-09)

  • #111065 -- Extract CMS query builder into DDA domain package
  • #111194 -- Gate remaining convertToCMSQueryType callsites behind CMS_DDA_QUERY_BUILDER

Feature flag: ff-cmsext-2041-dda-query-builder (FEATURE_FLAGS.CMS_DDA_QUERY_BUILDER)


Monitoring Links

DDA Query Builder Logs (warn-level)

Catches both DDA query builder threw (exceptions) and DDA query builder mismatch (divergence from baseline).

GraphQL Resolver Errors

The query builder runs inside resolver.ts for CMS GraphQL queries. Check for errors in that path.

CMS Item List / Schema Query Errors

convertToCMSQueryType is also called from schemaQuery.ts (item list handler path).

Broad Server Errors (sanity check)

General error rate for the server, in case the change causes unexpected downstream failures.

Feature Flag (Statsig)


What to Look For

Signal Meaning Action
DDA query builder threw Exception in buildFilterTerm for a field type/operator Coverage gap in packages/domains/cms/query-builder/src/filter.ts. Baseline is used (no user impact).
DDA query builder mismatch DDA result diverges from legacy builder Fix the mapping in filter.ts. Baseline is used (no user impact).
GraphQL resolver errors Unhandled exception in query path Potential user-facing issue. Check if related to the flag-gated code.
schemaQuery errors Errors in item list handler path Check convertToCMSQueryType callsite in schemaQuery.ts.

Both warn-level logs mean the fallback to baseline is working (users are unaffected), but they indicate gaps to fix in the DDA query builder package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment