SDK Versions

Error rate by installed SDK version · all projects — does the version explain the error, or do we?

rolled up 0s ago
On latest
62%
796 of 1,284 projects
latest is 4.2.1 · shipped Jul 22
Versions in production
5
oldest is 4.1.7 · 57 days old
every one is a support surface
Fleet error rate
0.23%
weighted across all versions
worst cohort is 4.2.1
Needs our fix
0
—
errors present on the latest build
488 projects run something older than 4.2.1. That is a support cost only where the error is actually fixed in a newer build — the matrix below separates those from ours.

Version cohorts

error rate per cohort · last 7d bar is share of the fleet
VersionFleet shareError rateErrors 7dvs latest
—

Error type × version

rate per 1k sessions · click a row for the action
A rate on every column means the version is not the cause — that one is ours. A rate on the newest column only means we shipped it. A rate that stops before the newest column is already fixed: those clients just need to update.

Action · —

—
—

—

Rate by version · per 1k sessions
First seen in
—
Fixed in
—
Events 7d
—
Projects hit
—
Open in SDK Errors →

Clients to nudge

stale + hitting a fixed error
—

Release log

Adoption is measured the day a project's beacon first reports the new version.

Prototype · figures are sample data for layout review, not production telemetry.