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.

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

Telegraf UI should join two or more plugins into one telegraf config #11527

Closed
ivankudibal opened this issue Jan 24, 2019 · 4 comments
Closed
Labels

Comments

@ivankudibal
Copy link
Contributor

Telegraf UI should join two or more plugins into one config

git: bd3c9cc (in master 4 after alpha)

Steps to reproduce:

  1. in new influxdb2, create eg docker telegraf plugin with endpoint unix:///var/run/docker.sock
  2. then create the second plugin, eg system one

This is the result in UI, there are two configs...
image

Observations:

  • There is no hint in the table which config is the docker one and which is the system one, because both the config lines are named equally. The two lines look like duplicity.
  • When I download one config and run telegraf, I can use system monitoring only
  • When I download the other config and run telegraf, I can use docker monitoring only

Proposed solution:

  • As user who has one telegraf I want influxdb2 to be able to provide me with just one config having both configurations in order I can listen to more than 1 plugin from one instance of telegraf.
  • As user I want to have version number in the config name or new column with timestamp, so that I do not see 2 lines with same information (duplicate lines) at the /organizations/034c0f2d08bc9000/collectors_tab

Workaround: do a manual join of the two configs on localhost

The issue seems to relate to #10771

@goller
Copy link
Contributor

goller commented Jan 24, 2019

good call @ivankudibal ... would be nice to have it only one configuration

@alexpaxton
Copy link
Contributor

@ivankudibal we are working on allowing users to name telegraf configs. Your suggestions are great, thank you for making an issue!

@stale
Copy link

stale bot commented Jul 23, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Jul 23, 2019
@stale
Copy link

stale bot commented Jul 30, 2019

This issue has been automatically closed because it has not had recent activity. Please reopen if this issue is still important to you. Thank you for your contributions.

@stale stale bot closed this as completed Jul 30, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants