support multiple td-agent instances with their own sets of configs?

[slvr32]

People occasionally ask if it's possible to run multiple instances of td-agent with separate configs, and the answer tends to be something like...

td-agent -c /some/path/td-agent1.conf
td-agent -c /some/other/path/td-agent2.conf

It might be nice if this puppet module supported this type of configuration, to be able to manage multiple instances of td-agent, with unique values for config_file, service_name, and other related config for each instance.

A practical use case would be alternate logging pipelines, e.g. where there's a need/want to keep logging pipelines separate for dev/testing/production, and running multiple td-agent instances is generally possible, but not currently supported by this puppet module.

[nmaludy]

@slvr32 I don't have an issue with this. I believe the trick would be to create a new systemd service file for additional configurations. Currently we just use the builtin systemd service packaged with the RPM. If you're interested in making these changes, i would happily review and work with you on a PR.

Thanks,
Nick