#ebpf_exporter
Live, measured metrics for the hashtag #ebpf_exporter from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #ebpf_exporter
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-29 23:11 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-29 23:11 UTCNo related tags with measured usage found for #ebpf_exporter.
Live pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-29 23:11 UTCEverything below is measured over the latest 8 public posts (spanning ~20380 hours).
Posting hours (UTC)
Languages: English (8)
Avg boosts / post: 0.3
Top of the latest posts
Have you ever though "boy I love distributed tracing, but I wish I could add kernel produced spans to my traces"? Well, now you can! I just published ebpf_exporter v2.4.0 and it can now create kernel spans that are integrated in your normal
Sneak peek: LBR based stacks in tracing spans for failed syscalls through ebpf_exporter. Think "retsnoop, but more structured". It be attached to existing traces too. Also pictured: SRSO sadness. #ebpf #kernel #ebpf_exporter
It's been too long since the last ebpf_exporter release, so I cut v2.5.0 today. https://github.com/cloudflare/ebpf_exporter/releases/tag/v2.5.0 #ebpf_exporter #ebpf #bpf #linux #kernel
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/ebpf_exporter