#dtrace
Live, measured metrics for the hashtag #dtrace from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #dtrace
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 · mastodon.online (Mastodon public tags API) · fetched 2026-09-26 11:38 UTC0 uses by 0 unique accounts across the window. Real per-day counts, not estimates. Newest bar is today so far.
Related hashtags
measured · mastodon.online (Mastodon public search API) · fetched 2026-09-26 11:38 UTCLive pulse
measured · mastodon.online (Mastodon tag timeline) · fetched 2026-09-26 11:38 UTCEverything below is measured over the latest 40 public posts (spanning ~13380 hours).
Posting hours (UTC) — busiest: 18:00
Languages: English (36) · German (2)
Avg boosts / post: 2.5
Top of the latest posts
#nextest now has support for USDT probes with #DTrace and #bpftrace, and it's so cool! https://nexte.st/docs/integrations/usdt/
In the spirit of developing in the open, here's the repo for the #dtrace inspired #commonlisp observability framework: https://github.com/MarceColl/CLTRACE
Exploring a #commonlisp native #dtrace inspired observability and debugging framework.
What “dtrace” means
WikipediaDTrace is a comprehensive dynamic tracing framework originally created by Sun Microsystems for troubleshooting kernel and application problems on production systems in real time. Originally developed for Solaris, it has since been released under the free Common Development and Distribution License (CDDL) in OpenSolaris and its descendant illumos, and has been ported to several other Unix-like systems. Windows Server systems from Windows Server 2025 will have DTrace as part of the system.
“DTrace” on Wikipedia (CC BY-SA) →#dtrace across platforms
every network with a public tag surfaceFollow #dtrace straight to each platform’s own tag page. Where a platform publishes open data we measure it above; the rest lock their numbers behind paid APIs, so we link rather than guess.
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/dtrace