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

InfluxDB 2.0: There is no way hot to configure Telegraf with my own plugin [area/api] #12672

Closed
bednar opened this issue Mar 18, 2019 · 6 comments

Comments

@bednar
Copy link
Contributor

bednar commented Mar 18, 2019

When I trying create a new Telegraf configuration with my own plugin than then the request fails:

-> POST 
-> http://127.0.0.1:9999/api/v2/telegrafs
-> {
	"name": "TelegrafConfig1552908917061-IT",
	"description": "test-config",
	"agent": {
		"collectionInterval": 1000
	},
	"plugins": [{
		"comment": "Output to Influx 2.0",
		"name": "influxdb_v2",
		"type": "output",
		"config": {
			"urls": ["http://127.0.0.1:9999"],
			"token": "$INFLUX_TOKEN",
			"organization": "my-org",
			"bucket": "my-bucket"
		}
	}, {
		"name": "kernel",
		"type": "input"
	}],
	"organizationID": "03899e997851e000"
}

<- 400 
<- Bad Request
<- {
	"code": "invalid",
	"message": "unsupported telegraf plugin ping-plugin, type input",
	"op": "unmarshal telegraf config raw plugin"
}
@stale
Copy link

stale bot commented Jul 26, 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 26, 2019
@russorat
Copy link
Contributor

+1

@stale stale bot removed the wontfix label Jul 26, 2019
@kelwang
Copy link
Contributor

kelwang commented Aug 7, 2019

So i have an idea about this one, currently if a invalid telegraf type posted, we will just show an error.
Alternatively, we can simply unmarshal it to a map[string]interface{}. In this way user may create whatever they want.

@stale
Copy link

stale bot commented Nov 5, 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 Nov 5, 2019
@danielnelson
Copy link
Contributor

+1

@bednar
Copy link
Contributor Author

bednar commented Jan 2, 2020

Fixed via #16132

@bednar bednar closed this as completed Jan 2, 2020
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

5 participants