Thanks for taking the time to answer.<p>&gt; I expect the gains to be around the legal and organisational stuff you need as a project grows (e.g. trademark registration, formal governance), as well as publicity.<p>Good point. It&#x27;s easy to forget the paperwork, but it certainly is important too!<p>&gt; Prometheus is perfect for monitoring any sort of operational timeseries, and is designed to do so in a way that scales both technically and organisationally.<p>Umm, yeah, but well, isn&#x27;t that the punchline of every monitoring project? ;-)<p>&gt; For example collectd is an on-host daemon that you have one of per machine. That may work when you&#x27;re small, but with many services that will become a bottleneck as each need to be added and stragglers may become an issue (Twitter seem to have hit this, see &quot;Lessons Learned&quot; <a href="https:&#x2F;&#x2F;blog.twitter.com&#x2F;2016&#x2F;observability-at-twitter-techn..." rel="nofollow">https:&#x2F;&#x2F;blog.twitter.com&#x2F;2016&#x2F;observability-at-twitter-techn...</a>). The Prometheus approach of one exporter per target scales far better.<p>I don&#x27;t understand. Isn&#x27;t that twitter blog essentially saying that they went from pull to push? Or is the main point here that they changed to have the agent on each host that collects everything on that host before transferring those metrics to the server (whether that&#x27;s push or pull)?<p>&gt; For another example if two different teams (say infra and database) have two different views of the world, with a collectd approach then the infra team likely wins. With Prometheus monitoring can be decentralised so infra can view a machine as mach1{rack=&quot;ch&quot;,datacenter=&quot;ma&quot;} and database as mach1{owner=&quot;app2&quot;,env=&quot;canary&quot;} each in their own Prometheus server. This gives teams more control by decentralising monitoring.<p>Good point. And I think this hits home in the sense that with our current monitoring setup the metrics we collect are really host-level, whereas for many metrics we&#x27;d rather have per-job (we&#x27;re a HPC shop, so a bit different from the usual web 2.0-stuff) statistics. But I&#x27;m not sure Prometheus bends to this either, since IIUC each metric is stored in a separate file, and if we&#x27;d have a bunch of metrics for each job ID in the system, this wouldn&#x27;t really work out, would it?