Skip to content

Conversation

@gakonst
Copy link
Contributor

@gakonst gakonst commented Feb 10, 2026

Summary

Adds detailed documentation about the --telemetry-url flag to the validator guide, explaining exactly what data is collected and what is not.

Motivation

We've been receiving repeated questions from validators about what the telemetry endpoint collects and whether it shares ambient machine information. This makes the answers explicit in the docs.

Slack thread: https://tempoxyz.slack.com/archives/C09KGTZ4S01/p1770750955165839

Changes

  • Added --telemetry-metrics-interval to the optional flags table
  • Added a new "Telemetry endpoint" section with:
    • What data types are exported (Prometheus metrics + OTLP logs)
    • Table of collected data categories (execution metrics, consensus metrics, operational logs)
    • Explicit "What is not collected" section confirming no hostname, IP, OS, or ambient machine data is sent

Testing

bun run check passes.

Adds a dedicated 'Telemetry endpoint' section explaining what data the
--telemetry-url flag collects (execution/consensus metrics and OTLP logs)
and explicitly states what is NOT collected (no hostname, IP, OS info,
or ambient machine data).

Co-authored-by: Jen <[email protected]>
Amp-Thread-ID: https://ampcode.com/threads/T-019c48fd-12ab-724e-a94c-2e11b2706265
Co-authored-by: Amp <[email protected]>
@vercel
Copy link

vercel bot commented Feb 10, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
tempo-docs Ready Ready Preview, Comment Feb 10, 2026 7:23pm

Request Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants