Component Telemetry

Design Systems & Engineering • Product Strategy & Growth

Component telemetry is data collected while design system components run in a product. Teams use it to observe where components appear, which versions or variants are in use, and what happens when people interact with them.

What can you measure?

Signal Question it answers
Static code and dependency inventory Which repositories reference a component, pass a particular prop, or depend on a package version?
Runtime usage In which instrumented apps did the component open or appear during the measurement period?
Runtime interaction or error events What happened after the component opened, such as a confirmation click or submission failure?

A code reference shows where to investigate. A runtime event shows that the instrumented behavior was observed. An error rate also needs a relevant denominator, such as failed submissions out of all recorded attempts. Define the event and the coverage before comparing products. For example, count apps that recorded at least one dialog open out of apps that report that event, and state the date range.

Example: Removing a deprecated Dialog prop

A design system team wants to remove a legacy Dialog prop. A code scan identifies repositories that still pass it. An event recorded when the dialog opens shows which instrumented products serve that configuration. The team uses both results to contact owners, prioritize migrations, and investigate gaps before scheduling removal.

Keep the payload tied to the decision. For this migration, a component identifier, package version, variant or legacy flag, and product identifier can be enough. Leave booking IDs, form input, and dialog content out of the event. Record what is instrumented so that an absence of events can be interpreted correctly.

Sources