The Scale Annual Price Displayed as $1.00
The in-product upgrade screen showed the Scale plan's annual price as $1.00/year. Checkout charged the correct amount, so anyone who continued saw the real figure at the payment step — a jarring gap on the screen where people decide.
The price is written in our catalogue as $1,000, and the parser that turns
display prices into amounts stopped reading at the thousands separator. It was
the only price in the catalogue with one, which is why Scale annual was the
only plan affected.
Prices with separators now parse correctly, malformed entries are reported rather than silently becoming zero, and amounts are rounded rather than truncated.
Failed Requests No Longer Show as Successful
A request that failed upstream could appear in Traces as success while reporting an error count at the same time. A trace's status was read only from its root span, and provider failures are recorded on a child span, so the failure was visible in the count but not in the status.
Around nine in ten failed traces were affected. Any dashboard, filter or alert keyed on trace status was undercounting failures.
Status now reflects an error anywhere in the trace, and recognises both spellings of the OpenTelemetry status field that our ingest paths produce — the second of which accounted for the large majority of error spans and was never being matched.
This corrects historical traces as well as new ones, since the status is derived at read time.