Grafana public trace evaluation for API prototypes — Hovvi

How Grafana lets builders search a public trace, open one request and inspect its status, duration, services and spans before account or production telemetry setup.

Published by Hovvi Research. Observed ; materially updated .

What happened

Use a no-login sample trace to move from a query result to one request, its outcome, duration, service path and spans; place account and production telemetry setup after the user understands the diagnostic value. Let a prospect inspect a real distributed request and its span relationships before asking them to create an account or connect production telemetry.

Evidence

A real request becomes inspectable before production setup.

StageWhat the builder can doCommitment boundary
EnterOpen a public Grafana instanceNo login or setup
SearchQuery current traces by service and trace fieldsUses hosted sample telemetry
InspectOpen one Trace ID and read request, status, timing and servicesNo private telemetry connected
DiagnoseExpand the span tree and inspect operationsProduction instrumentation still separate

The trace answers four questions an API demo usually leaves open.

QuestionObserved fieldPrototype use
Did the request complete?HTTP status and root operationShow outcome, not only a loading state
How long did it take?Trace duration and elapsed timelineLocate the user-visible delay
Which services participated?Service count and span treeExpose the real dependency path
Where should debugging start?Service, operation and span metadataLink failure to the smallest inspectable unit

Public sample telemetry proves the interaction, not the user's system.

The sandbox can prove how trace search and inspection work without collecting private data. A product must label the sample clearly and ask for account, instrumentation and production permissions only when the user chooses to validate their own system.

Observed facts

  • Grafana's quick-start documentation directs users to play.grafana.org as a public instance that requires no setup or login.
  • The public Explore surface presents itself as a live query sandbox for metrics, logs, traces and profiles; creating a Grafana Cloud account remains a separate action.
  • Grafana's documented trace workflow selects the hosted traces data source, chooses Search, filters by service, runs the query and opens a Trace ID to inspect one request.
  • Grafana describes traces as a map of a request path through distributed services that exposes timing and service relationships, rather than only an aggregate chart.
  • The trace view exposes a Trace ID, start time, duration and service count, then organizes individual spans by service, operation and elapsed time; selecting a span reveals its detailed metadata.
  • In the no-login public sandbox observed on 2026-08-28, a live quickpizza POST /api/pizza trace exposed HTTP 200, 81.13 ms total duration, four services and 49 spans. These values are a dated example, not a persistent performance claim.

Editorial inference

  • An API prototype becomes more credible when its public evaluation proves a real cross-service request path before asking for private telemetry, provided the sample is clearly labeled and never presented as the user's production state.

Evidence views

  1. Public sample-data entry
  2. Trace search with service and duration filters
  3. Trace results with request identity
  4. Selected trace overview with status, duration and services
  5. Span timeline and service-operation tree
  6. Production telemetry setup boundary

Founder takeaway

Prove one real request path before asking for telemetry: outcome, timing, services and spans should be inspectable, and sample data must remain clearly separate from production.

Use when

  • A prototype depends on multiple API or Agent services
  • A user must judge observability value before sharing private telemetry
  • The product can provide clearly labeled synthetic or public sample data
  • A failure needs to be attributable to a service or operation

Avoid when

  • Sample telemetry could be mistaken for the user's production system
  • The trace omits the request outcome or participating services
  • Sensitive payloads are exposed in a public sample
  • The product promises production performance from a dated demo trace

Next implementation step

Design a public observability proof that lets a prospect inspect one API request across services before connecting private telemetry.

Acceptance criteria

  • A visitor can run or inspect a trace query without creating an account
  • The selected request exposes status, duration and participating services
  • A visitor can expand the span relationship to locate one operation
  • The interface states that the data is public sample telemetry
  • Production telemetry connection is a separate explicit step
  • No private telemetry, credential or authenticated account state appears in the public reference

Related cases

  • Observe the path versus execute the first request: Cloudflare Workers Playground first-run flow — Hovvi

    Cloudflare lets a visitor execute and recover a first API request before deployment, while Grafana lets a visitor inspect the resulting cross-service path before connecting production telemetry; together they separate functional proof from operability proof.

  • Protected review versus public sample proof: Vercel preview external-sharing boundary — Hovvi

    Grafana offers a public sample environment before private telemetry setup, while Vercel documents an owner-scoped preview for a named or link-enabled external reviewer. Both support evaluation before commitment, but public product proof must not be confused with access to a specific protected build.

Version history

Current snapshot: snap_grafana_public_trace_evaluation_2026_08_28 — Added a bounded link-only Grafana public-trace evaluation reference backed by official documentation and a dated real-browser observation; no private telemetry, authenticated state or copied screenshot is retained.

Use with an Agent

Example read-only MCP query:

Retrieve the Hovvi Founder case fc_grafana_public_trace_evaluation_2026_08 with observed facts, evidence screens, applicability limits and citations.