Skip to content

SYSTEM Cited by 1 source

Grafana Faro

What it is

Grafana Faro (github.com/grafana/faro-web-sdk) is Grafana Labs' open-source frontend observability web SDK. It captures errors, performance data, user events, and logs from the browser and ships them to a Grafana-compatible backend (Loki / Tempo / Prometheus), with OpenTelemetry interoperation.

Why it's on the wiki

Zalando's engineers evaluated Faro while building their own browser observability SDK and flagged it as "a great package to check out if you are starting from scratch" — an explicit alternative recommendation for greenfield teams (Source: ).

Zalando chose not to adopt Faro because they already had instrumentation architecture in flight (OpenTracing migration, the split @zalando/observability-api package, the systems/zalando-observability-sdk-node already built) and needed tight integration with the Rendering Engine — not a quality judgement on Faro.

Stub

Full Faro architecture (Collector, agents, instrumentation packages) is not covered on this page; this is a stub for cross-reference only.

Seen in

  • sources/2026-04-29-grafana-get-observability-in-the-terminal-for-you-and-your-agents-with-the-gcx-cli-tool — Faro is one of the four lifecycle axes exposed by gcx. Named verbatim: "Onboard a Faro-instrumented frontend, create the app, and manage sourcemaps so stack traces are readable." Canonicalises Faro as the frontend-observability substrate an agent-driven CLI workflow can bootstrap end-to-end — including sourcemap management, which is the typically- painful last-mile step for stack-trace-readable frontend observability.
  • — recommended by Zalando engineers as a greenfield alternative to their internal SDK.
Last updated · 542 distilled / 1,571 read