Subject: [InfluxData Community] [Welcome & Getting Started] Is it possible to merge or (combine) .conf files with an override behavior

> But the .conf in your example doesn’t have outputs. This means that outputs (or any other setting?) defined in /etc/telegraf/telegraf.conf apply to all .conf files in /etc/telegraf/telegraf.d/? The “combined into a single config” you mentioned?

I have my outputs added in another ansible task, but yeah, all the files in telegraf.conf and the various files in telegraf.d are merged into one big config.

> But .conf files in /etc/telegraf/telegraf.d/ work as separate entities? So if I had a bunch of .conf files in /etc/telegraf/telegraf.d/ with full workflow settings, do they work in isolation or all [tables] will be combined in one big mix?

It's one big mix.  By default all data produced by all inputs is sent to all outputs, so in your example you must use metric filtering.  TBH, I wasn't so sure about the metric filtering either when I started working on Telegraf, but I've come to find that it works quite well, its flexible and doesn't add hardly any runtime overhead like having multiple workflows would.  I try to think about routing metrics based on their properties and less about what plugin produced them.