REDIS / ADBC DRIVER

Adoption analytics

Opt-in reporting installations · Last 28 days unless labeled · Organization and team labels are self-reported, not verified identities.

Query mix and reliability

One attempt = one ExecuteQuery/ExecuteUpdate call, including an entire script or parameter batch. Success requires result exhaustion. Latency includes application fetch time; histogram percentiles are upper bounds.

Organizations, teams and applications

SQL features

Top-level SELECT features; one execution may use several features. Nested query bodies are not included.

Daily activity

UTC collector receipt date. Offline or delayed reports may move activity into a later day.

Download snapshots

Downloads measure distribution activity, not unique users. GitHub build assets may be fetched by packaging jobs. Channels are shown separately.

Week-4 retention: installations with a successful execution 28–35 days after their first observed successful execution; only cohorts with the full 35-day window are eligible. Installation IDs must remain stable. Missing telemetry, blocked networks and opt-out users are outside this view.