#collectd
Live, measured metrics for the hashtag #collectd from the open social web. Every number carries a named source and the time it was fetched. Nothing is estimated.
Own #collectd
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 16:27 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 16:27 UTCLive pulse
measured · fosstodon.org (Mastodon tag timeline) · fetched 2026-07-28 16:27 UTCEverything below is measured over the latest 22 public posts (spanning ~63312 hours).
Posting hours (UTC) — busiest: 10:00
Languages: English (18) · French (3) · German (1)
Avg boosts / post: 0.3
Top of the latest posts
@jcamos I used to rely on #collectd (with the #Riemann writter) but switched to riemann-tools (which happens to be more hackable for me and has saner defaults) to collect metrics. Downstream, Riemann does some processing and alerting (it is
@jhx #telegraf + #influxdb + #grafana I used #collectd, but it has no support for caching during network outages and weird metrics naming conventions. #telegraf seems to be much nicer to configure.
Stupid (not) nerd thing of the day: have #collectd regularly run a #curl command that tells #uptimekuma the server hidden far deep behind NAT is still alive.
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/collectd