#opentelemetry
Live, measured metrics for the hashtag #opentelemetry from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #opentelemetry
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 · mas.to (Mastodon public tags API) · fetched 2026-07-27 00:35 UTC8 uses by 8 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mas.to (Mastodon public search API) · fetched 2026-07-27 00:35 UTCLive pulse
measured · mas.to (Mastodon tag timeline) · fetched 2026-07-27 00:35 UTCEverything below is measured over the latest 40 public posts (spanning ~1128 hours).
Posting hours (UTC) — busiest: 14:00
Languages: English (37) · Russian (1) · French (1) · Spanish (1)
Avg boosts / post: 0.5
Top of the latest posts
@pertho I think @0xc has done some work on #OpenTelemetry and #PHP, so maybe he can point you to some good information. 🙂
📢 OpenTelemetry community: all Zoom meetings are moving to the LFX Project Control Center. Please update your calendars. Issues or questions? Comment on the tracking issue or ask in #opentelemetry on CNCF Slack. 🔗 https://github.com/open-
RE: https://peoplemaking.games/@True/116870032728771000 I did it, LGTM stack wasn't too complicated. Learning #OpenTelemetry is a helpful skill, I suspect OTel with be sticking around long-term. I love being able to drill down into traces!
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/opentelemetry