You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our Telegraf deployment, we run Telegraf using the --config-directory flag to load multiple configuration files. During initialization, Telegraf logs the counts of loaded inputs, outputs, aggregators, processors, and secretstores. However, with a large number of configuration files, it becomes challenging to trace which plugin is sourced from which file, making debugging and troubleshooting more difficult.
Expected behavior
Show file name from where the plugin was loaded
Actual behavior
Only file name and plugin count printed at startup.
Additional info
To some extent it is closely related to #12827 and #15732
The text was updated successfully, but these errors were encountered:
Use Case
In our Telegraf deployment, we run Telegraf using the
--config-directory
flag to load multiple configuration files. During initialization, Telegraf logs the counts of loaded inputs, outputs, aggregators, processors, and secretstores. However, with a large number of configuration files, it becomes challenging to trace which plugin is sourced from which file, making debugging and troubleshooting more difficult.Expected behavior
Show file name from where the plugin was loaded
Actual behavior
Only file name and plugin count printed at startup.
Additional info
To some extent it is closely related to #12827 and #15732
The text was updated successfully, but these errors were encountered: