Post #1495854
2026-03-13 08:48 UTC
The need for having these bespoke agents in the middle whose only job is to query metrics in some local, service specific way, and publish them in a a more generic, abstract way is something that always irked me.
systemd's own functionality for example is typically monitored via D-Bus, and the complexity of linking that up with things like prometheus, via purpose-written agents is just not that great.
With systemd v260 we are trying to move things into a better direction on this front:
Replies (1)
-
@pid_eins@mastodon.social 2026-03-13 08:51
instead of expecting those agents to understand every relevant services and their semantics individually, what if those services would all just implement the same, generic interface that allows pulling out the metrics you want in a normalized, unified way? Hence, in systemd v260 we now introduced a very simple way to do this: there's now a new directory: /run/systemd/report/. Every local service can bind an AF_UNIX socket in there if they like, and implement the same, very…