New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not able able to read the multiple telegraf.conf placed inside the telegraf.d directory #9093
Comments
Hi, what command are you using to start telegraf? I'm able to get the expected behavior if I add the following flag: |
I am using docker container for telegraf so just using the |
Looks like according to this thread: #5656 (comment) you can do the run docker command and pass the argument I mentioned and it should send it to telegraf, let me know if that's a possibility |
can you tell me how to pass this command in docker-compose because I tried pass using args and using environment as well but it's not working ? |
we have to pass in docker-compose like below example
|
System info:
telegraf version - 1.18.0
InfluxDB - quay.io/influxdb/influxdb:v2.0.4
Docker
Steps to reproduce:
/etc/telegraf/telegraf.d/enum-telegraf.conf
and/etc/telegraf/telegraf.d/kinesis-telegraf.conf
. In kinesis-telegraf.conf, I have defined all my input plugins[[inputs.kinesis_consumer]]
and output plugins[[outputs.influxdb_v2]]
. In enum-telegraf.conf I have put my processor plugin[[processors.enum]]
only/etc/telegraf/telegraf.conf
. In main telegraf.conf I have put nothing else except the name of output plugin[[outputs.influxdb_v2]]
because we can't keep file empty.Expected behavior:
telegraf should run fine and do the work as defined in both the
telegraf.conf
Actual behavior:
It's giving errors and not able to read anything from the telegraf.d directory.
the following content is stored in the enum-telegraf.conf
I have tested the content of both telegraf.conf files and both are working fine if we place both inside a giant telegraf.conf file.
The text was updated successfully, but these errors were encountered: