1992235 - Data Review: Glean ping for Android Rust Component Errors

Status: NEW

(Application Services :: General, enhancement)

Description

[Ben Dean-Kawamura [:bdk]]

Create a new Glean ping named rust-component-errors with the following metrics:

• error-type (string): A unique string that identifies and groups the error. This works similar to a crash fingerprint, except it’s manually defined by the programmers. Error types strings start with the component name and use snake-casing (for example logins-deserialize-error or places-bookmark-corruption).
• message (string): Error message string with details. This is generated from the Rust debug format string.
• breadcrumbs (string or string_list): String containing breadcrumb information. The Rust code can record breadcrumbs which serve as context for errors. The most recent 20 breadcrumb strings will be joined into a single string.

Events will be rate limited to 20 events per component/user/day. Rust errors are not fatal, so it’s easy to get into a state where the same error is continuously emitted. This should be enough to limit the volume in these cases.

The main reason for switching to Glean is that Desktop can also send these events to glean. A secondary reason is that we won't be using other team's Sentry boards. See https://docs.google.com/document/d/1aK9AhYP65rEwADvx5vRiSC_RCtMfaZOBfoZDPKPThVk/edit?tab=t.0 for details.

Let's continue to send errors to Sentry as well until we have the new Glean-based error dashboards in place.