Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Show loaded plugins source information(http or file) #16269

Closed
neelayu opened this issue Dec 6, 2024 · 3 comments · Fixed by #16270
Closed

Show loaded plugins source information(http or file) #16269

neelayu opened this issue Dec 6, 2024 · 3 comments · Fixed by #16270
Labels
feature request Requests for new plugin and for new features to existing plugins

Comments

@neelayu
Copy link
Contributor

neelayu commented Dec 6, 2024

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
@neelayu neelayu added the feature request Requests for new plugin and for new features to existing plugins label Dec 6, 2024
@neelayu neelayu mentioned this issue Dec 6, 2024
Merged
1 task
@Hipska
Copy link
Contributor

Hipska commented Mar 27, 2025

I feel like this request is implemented in a wrong way.

To me this looks much more applicable for a separate command, rather than an option when starting/running telegraf. The command could look like telegraf config source or maybe telegraf config check source. As it seems there is currently no way to retrieve this table without actually starting the plugins, which feels like a shame.

What do you all think?

cc @mstrandboge @srebhan

@neelayu
Copy link
Contributor Author

neelayu commented Mar 27, 2025

I get your point. But in your case, we still have to pass in the necessary flags --config and --config-directory, right?

@Hipska
Copy link
Contributor

Hipska commented Mar 27, 2025

Yes of course! (unless you only want to load the default /etc/telegraf/telegraf.conf)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature request Requests for new plugin and for new features to existing plugins
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(agent): Print plugins source information neelayu/telegraf
2 participants
@Hipska @neelayu