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

Question: do you plan to integrate it into telegraf? #61

Closed
gaetanquentin opened this issue Feb 18, 2018 · 1 comment
Closed

Question: do you plan to integrate it into telegraf? #61

gaetanquentin opened this issue Feb 18, 2018 · 1 comment

Comments

@gaetanquentin
Copy link

Do you plan to integrate this good tool as a plugin into telegraf (written oin go too) ?

@sofixa
Copy link
Member

sofixa commented Mar 11, 2018

Hi,

That was my original idea but i had a hard time going around some issues(mostly how to correlate the telegraf interval and vSphere's metric collection interval, plus different development cycles). Currently at work we use it with telegraf as a relay(vsphere-influxdb-go executes every minute and sends to a telegraf tcp listener in InfluxDB format, which then relays based on tags to a few InfluxDBs) to profit some of telegraf's nice features(caching, easy filtering/sharding).

Now that the tool is more or less stable(there are some feature requests and bugs, but general basic functionality is there), it might be a good idea to split the vSphere collection functions into a library, and add it as a telegraf plugin while also maintaining this project as a standalone tool without code duplication. However, i don't have a lot of free time currently, and i prefer to spend it in adding extra features and fixing #55 which is proving to be a hard one to tackle.

TL;DR: I think i might be a good idea, but it will require some refactoring and i don't have the time now, but might look into it in the future

Cheers,
Adrian

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants