#spans
Live, measured metrics for the hashtag #spans from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #spans
This #name is available to claim. It becomes your portal on the open agent web: this very page, a keyword you rank for by an open public stake, and a verifiable identity for AI agents. Nobody else sells a page like this for every #name.
Day-by-day usage
measured · fosstodon.org (Mastodon public tags API) · fetched 2026-07-28 19:26 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · fosstodon.org (Mastodon public search API) · fetched 2026-07-28 19:26 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 19:26 UTCEverything below is measured over the latest 10 public posts (spanning ~22649 hours).
Posting hours (UTC)
Languages: English (10)
Avg boosts / post: 0.3
Top of the latest posts
Most engineers instrument spans. Far fewer think about whether those #spans are actually useful. If your traces are noisy, inconsistent, or missing context, they stop being debugging tools and become expensive timelines. New deep dive on #O
Ever notice how every project now “supports #OpenTelemetry”? 🤔 There’s a big gap between exporting a few #spans and real, production-grade #telemetry. In the Code RED Newsletter, @[email protected] breaks down what OTel maturit
Semantic Conventions for #GenAI agent and framework #spans https://opentelemetry.io/docs/specs/semconv/gen-ai/gen-ai-agent-spans/ #OpenTelemetry #LLM
Every number above is measured from a named public API at the shown fetch time. Nothing is estimated or extrapolated. Platforms that lock their data behind paid APIs are not shown. Agents: the same numbers, as JSON, at /api/hashtags/spans