Telegraph Auto Start - How to guide, should the telepgraph service be running?

1

I have InfluxDB v2.7.1 running and configured a Telegraph configuration that fetches MQTT data, this works perfect if I start telegraph using:

telegraf --config http://192.168.3.165:8086/api/v2/telegrafs/0bc28cac32b8e000

What I would like to try and understand is how Telegraph Configurations work, it appears that I can create multiple configurations but they point is how to automatically start a configuration when the service starts, my one configuration is not started automatically.

Should Telegraph configurations be running as services on Linux, if they should mine is failing?

journalctl -u telegraf.service

Sep 03 08:15:51 db-app-server systemd[1]: Starting Telegraf…
Sep 03 08:15:53 db-app-server telegraf[783]: 2023-09-03T08:15:53Z I! Loading config: /etc/telegraf/telegraf.conf
Sep 03 08:15:53 db-app-server telegraf[783]: 2023-09-03T08:15:53Z E! [telegraf] Error running agent: no outputs found, did y>
Sep 03 08:15:53 db-app-server systemd[1]: telegraf.service: Main process exited, code=exited, status=1/FAILURE
Sep 03 08:15:53 db-app-server systemd[1]: telegraf.service: Failed with result ‘exit-code’.
Sep 03 08:15:53 db-app-server systemd[1]: Failed to start Telegraf.
Sep 03 08:15:53 db-app-server systemd[1]: telegraf.service: Scheduled restart job, restart counter is at 1.
Sep 03 08:15:53 db-app-server systemd[1]: Stopped Telegraf.

Thank you in advance for any suggestions.

2

Hello @a18041967,
yes you are required to pass in a configuration, Without it telegraf doesn’t know which plugins to use.
The agent starts, then scans the config for the plugins you want to use, then loads the plugins, then starts running them.
You can use the --debug flag with your command with a config to see more detail on what telegraf is doing.