Daniel Nelson

You can of course run the container with `--config-directory /etc/telegraf/telegraf.d` set, any arguments are passed to Telegraf. I think this really boils down to deciding if the `--config-directory` option should...

You can run the container with `--config-directory /etc/telegraf/telegraf.d`.

Here it is including volume mount options: ``` docker run -v /telegraf.conf:/etc/telegraf/telegraf.conf -v /telegraf.d:/etc/telegraf/telegraf.d telegraf --config-directory /etc/telegraf/telegraf.d ```

I don't think we should add the Context to the Accumulator as it is only available in inputs and aggregators. Instead the Context should be passed in to the Start/Gather...

Obviously what I'm proposing is more work, in the meantime we have been creating a background/todo context in the Start function and cancelling it in Stop.

I've seen this before on AWS EC2 and in LXC, it every case so far it was tracked back to the values in `/proc/stat` decreasing, which should never happen, but...

Might be helpful to enable `collect_cpu_time` to get the save the raw jiffies. Since this is usually happening on usage_guest and usage_user, are these systems both qemu hosts? FWIW I'm...

I don't believe the library we are using, gopsutil, can get this information yet. Someone needs to investigate how this data can be acquired and propose a change to the...

It looks like the threads can be read in the same way to processes from `/proc/$LWP`. I'll bet this means we would only need to expose an option to search...

I don't think there is any reason this could not be done, I see this as being a new input plugin specifically for events. fyi @prydin @puckpuck For SNMP traps...