Christopher J. Morrone

Also, the daemons should look for the configuration file in a known, standard system location by default. This can be overridden by specifying a different configuration file on the command...

> There is a practical solution to this which is already available-- use the genders-based systemd ldms configuration shipped with the ldmsd rpms. > > So assuming you're already aware...

I don't particularly care at this stage what the specific configuration file format looks like, but I can give some early guidance. It needs to be something reasonably human readable...

json is a data interchange format, so yes of course it works well as wire protocol. But it does not work well for configuration files. In particular, json has no...

Another requirement that just came to mind: When a bad value is encountered (not just a syntax error) in the configuration file, the daemon needs to be able to return...

I would like to see the parts where different nodes are configured in the same file removed. I completely see what you are going for, @tom95858. I think in broad...

I am going to suggest using TOML as the base configuration language: https://github.com/toml-lang/toml

> The aggregators (and the bits that monitor them) need to be able to discover (without relying on samplers to connect to them for discovery) what they are supposed to...

Having to coordinate things like ports, transports, etc. is not complicated. It is the sort of thing that system administrators do all the time for any number of services running...

I created TOML versions of two of @baallan's "relaxed json" examples. It think I would suggest more changes in the end, but at least they server as a general example...